From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Move tasklet kicking to __i915_request_queue caller
Date: Thu, 15 Aug 2019 14:35:37 +0300 [thread overview]
Message-ID: <877e7e7jau.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190815042031.27750-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Since __i915_request_queue() may be called from hardirq (timer) context,
> we cannot use local_bh_disable/enable at the lower level. As we do want
> to kick the tasklet to speed up initial submission or preemption for
> normal client submission, lift it to the normal process context
> callpath.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_request.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index 4021334dd2c5..8a2bc1d317e4 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -1203,12 +1203,10 @@ void __i915_request_queue(struct i915_request *rq,
> * decide whether to preempt the entire chain so that it is ready to
> * run at the earliest possible convenience.
> */
> - local_bh_disable();
> i915_sw_fence_commit(&rq->semaphore);
> if (attr && rq->engine->schedule)
> rq->engine->schedule(rq, attr);
> i915_sw_fence_commit(&rq->submit);
> - local_bh_enable(); /* Kick the execlists tasklet if just scheduled */
Was this here to only optimize the latency from schedule
to resubmission?
Or is it actually guarding something?
-Mika
> }
>
> void i915_request_add(struct i915_request *rq)
> @@ -1247,7 +1245,9 @@ void i915_request_add(struct i915_request *rq)
> if (list_empty(&rq->sched.signalers_list))
> attr.priority |= I915_PRIORITY_WAIT;
>
> + local_bh_disable();
> __i915_request_queue(rq, &attr);
> + local_bh_enable(); /* Kick the execlists tasklet if just scheduled */
>
> /*
> * In typical scenarios, we do not expect the previous request on
> --
> 2.23.0.rc1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-15 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 4:20 [PATCH] drm/i915: Move tasklet kicking to __i915_request_queue caller Chris Wilson
2019-08-15 5:02 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-08-15 11:35 ` Mika Kuoppala [this message]
2019-08-15 11:43 ` [PATCH] " Chris Wilson
2019-08-15 12:24 ` Mika Kuoppala
2019-08-15 21:03 ` ✓ Fi.CI.IGT: success for " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e7e7jau.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox