From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 4/4] drm/i915/gt: Remove timeslice suppression
Date: Wed, 6 Jan 2021 15:57:49 +0000 [thread overview]
Message-ID: <0ed63aeb-d58e-5ec6-2072-65d17be612dc@linux.intel.com> (raw)
In-Reply-To: <20210106123939.18435-4-chris@chris-wilson.co.uk>
On 06/01/2021 12:39, Chris Wilson wrote:
> In the next^W future patch, we remove the strict priority system and
> continuously re-evaluate the relative priority of tasks. As such we need
> to enable the timeslice whenever there is more than one context in the
> pipeline. This simplifies the decision and removes some of the tweaks to
> suppress timeslicing, allowing us to lift the timeslice enabling to a
> common spot at the end of running the submission tasklet.
>
> One consequence of the suppression is that it was reducing fairness
> between virtual engines on an over saturated system; undermining the
> principle for timeslicing.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2802
> Testcase: igt/gem_exec_balancer/fairslice
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/gt/intel_engine_types.h | 10 -
> .../drm/i915/gt/intel_execlists_submission.c | 173 +++++++-----------
> 2 files changed, 68 insertions(+), 115 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_types.h b/drivers/gpu/drm/i915/gt/intel_engine_types.h
> index 430066e5884c..df62e793e747 100644
> --- a/drivers/gpu/drm/i915/gt/intel_engine_types.h
> +++ b/drivers/gpu/drm/i915/gt/intel_engine_types.h
> @@ -238,16 +238,6 @@ struct intel_engine_execlists {
> */
> unsigned int port_mask;
>
> - /**
> - * @switch_priority_hint: Second context priority.
> - *
> - * We submit multiple contexts to the HW simultaneously and would
> - * like to occasionally switch between them to emulate timeslicing.
> - * To know when timeslicing is suitable, we track the priority of
> - * the context submitted second.
> - */
> - int switch_priority_hint;
> -
> /**
> * @queue_priority_hint: Highest pending priority.
> *
> diff --git a/drivers/gpu/drm/i915/gt/intel_execlists_submission.c b/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
> index ba3114fd4389..50d4308023f3 100644
> --- a/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
> +++ b/drivers/gpu/drm/i915/gt/intel_execlists_submission.c
> @@ -1143,25 +1143,6 @@ static void defer_active(struct intel_engine_cs *engine)
> defer_request(rq, i915_sched_lookup_priolist(engine, rq_prio(rq)));
> }
>
> -static bool
> -need_timeslice(const struct intel_engine_cs *engine,
> - const struct i915_request *rq)
> -{
> - int hint;
> -
> - if (!intel_engine_has_timeslices(engine))
> - return false;
> -
> - hint = max(engine->execlists.queue_priority_hint,
> - virtual_prio(&engine->execlists));
> -
> - if (!list_is_last(&rq->sched.link, &engine->active.requests))
> - hint = max(hint, rq_prio(list_next_entry(rq, sched.link)));
> -
> - GEM_BUG_ON(hint >= I915_PRIORITY_UNPREEMPTABLE);
> - return hint >= effective_prio(rq);
> -}
> -
> static bool
> timeslice_yield(const struct intel_engine_execlists *el,
> const struct i915_request *rq)
> @@ -1181,76 +1162,68 @@ timeslice_yield(const struct intel_engine_execlists *el,
> return rq->context->lrc.ccid == READ_ONCE(el->yield);
> }
>
> -static bool
> -timeslice_expired(const struct intel_engine_execlists *el,
> - const struct i915_request *rq)
> +static bool needs_timeslice(const struct intel_engine_cs *engine,
> + const struct i915_request *rq)
> {
> + if (!intel_engine_has_timeslices(engine))
> + return false;
> +
> + /* If not currently active, or about to switch, wait for next event */
> + if (!rq || __i915_request_is_complete(rq))
> + return false;
> +
> + /* We do not need to start the timeslice until after the ACK */
> + if (READ_ONCE(engine->execlists.pending[0]))
> + return false;
> +
> + /* If ELSP[1] is occupied, always check to see if worth slicing */
> + if (!list_is_last_rcu(&rq->sched.link, &engine->active.requests))
> + return true;
> +
> + /* Otherwise, ELSP[0] is by itself, but may be waiting in the queue */
> + if (!RB_EMPTY_ROOT(&engine->execlists.queue.rb_root))
> + return true;
> +
> + return !RB_EMPTY_ROOT(&engine->execlists.virtual.rb_root);
> +}
> +
> +static bool
> +timeslice_expired(struct intel_engine_cs *engine, const struct i915_request *rq)
> +{
> + const struct intel_engine_execlists *el = &engine->execlists;
> +
> + if (i915_request_has_nopreempt(rq) && __i915_request_has_started(rq))
> + return false;
> +
> + if (!needs_timeslice(engine, rq))
> + return false;
> +
> return timer_expired(&el->timer) || timeslice_yield(el, rq);
> }
>
> -static int
> -switch_prio(struct intel_engine_cs *engine, const struct i915_request *rq)
> -{
> - if (list_is_last(&rq->sched.link, &engine->active.requests))
> - return engine->execlists.queue_priority_hint;
> -
> - return rq_prio(list_next_entry(rq, sched.link));
> -}
> -
> -static inline unsigned long
> -timeslice(const struct intel_engine_cs *engine)
> +static unsigned long timeslice(const struct intel_engine_cs *engine)
> {
> return READ_ONCE(engine->props.timeslice_duration_ms);
> }
>
> -static unsigned long active_timeslice(const struct intel_engine_cs *engine)
> -{
> - const struct intel_engine_execlists *execlists = &engine->execlists;
> - const struct i915_request *rq = *execlists->active;
> -
> - if (!rq || __i915_request_is_complete(rq))
> - return 0;
> -
> - if (READ_ONCE(execlists->switch_priority_hint) < effective_prio(rq))
> - return 0;
> -
> - return timeslice(engine);
> -}
> -
> -static void set_timeslice(struct intel_engine_cs *engine)
> +static void start_timeslice(struct intel_engine_cs *engine)
> {
> + struct intel_engine_execlists *el = &engine->execlists;
> unsigned long duration;
>
> - if (!intel_engine_has_timeslices(engine))
> - return;
> + /* Disable the timer if there is nothing to switch to */
> + duration = 0;
> + if (needs_timeslice(engine, *el->active)) {
> + if (el->timer.expires) {
Why not just timer_pending check? Are you sure timer->expires cannot
legitimately be at jiffie 0 in wrap conditions?
> + if (!timer_pending(&el->timer))
> + tasklet_hi_schedule(&engine->execlists.tasklet);
> + return;
> + }
>
> - duration = active_timeslice(engine);
> - ENGINE_TRACE(engine, "bump timeslicing, interval:%lu", duration);
> + duration = timeslice(engine);
> + }
>
> - set_timer_ms(&engine->execlists.timer, duration);
> -}
> -
> -static void start_timeslice(struct intel_engine_cs *engine, int prio)
> -{
> - struct intel_engine_execlists *execlists = &engine->execlists;
> - unsigned long duration;
> -
> - if (!intel_engine_has_timeslices(engine))
> - return;
> -
> - WRITE_ONCE(execlists->switch_priority_hint, prio);
> - if (prio == INT_MIN)
> - return;
> -
> - if (timer_pending(&execlists->timer))
> - return;
> -
> - duration = timeslice(engine);
> - ENGINE_TRACE(engine,
> - "start timeslicing, prio:%d, interval:%lu",
> - prio, duration);
> -
> - set_timer_ms(&execlists->timer, duration);
> + set_timer_ms(&el->timer, duration);
> }
>
> static void record_preemption(struct intel_engine_execlists *execlists)
> @@ -1363,16 +1336,16 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> __unwind_incomplete_requests(engine);
>
> last = NULL;
> - } else if (need_timeslice(engine, last) &&
> - timeslice_expired(execlists, last)) {
> + } else if (timeslice_expired(engine, last)) {
> ENGINE_TRACE(engine,
> - "expired last=%llx:%lld, prio=%d, hint=%d, yield?=%s\n",
> - last->fence.context,
> - last->fence.seqno,
> - last->sched.attr.priority,
> + "expired:%s last=%llx:%lld, prio=%d, hint=%d, yield?=%s\n",
> + yesno(timer_expired(&execlists->timer)),
> + last->fence.context, last->fence.seqno,
> + rq_prio(last),
> execlists->queue_priority_hint,
> yesno(timeslice_yield(execlists, last)));
>
> + cancel_timer(&execlists->timer);
What is this cancel for?
Regards,
Tvrtko
> ring_set_paused(engine, 1);
> defer_active(engine);
>
> @@ -1408,7 +1381,6 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> * of timeslices, our queue might be.
> */
> spin_unlock(&engine->active.lock);
> - start_timeslice(engine, queue_prio(execlists));
> return;
> }
> }
> @@ -1435,7 +1407,6 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> if (last && !can_merge_rq(last, rq)) {
> spin_unlock(&ve->base.active.lock);
> spin_unlock(&engine->active.lock);
> - start_timeslice(engine, rq_prio(rq));
> return; /* leave this for another sibling */
> }
>
> @@ -1599,29 +1570,23 @@ static void execlists_dequeue(struct intel_engine_cs *engine)
> execlists->queue_priority_hint = queue_prio(execlists);
> spin_unlock(&engine->active.lock);
>
> - if (submit) {
> - /*
> - * Skip if we ended up with exactly the same set of requests,
> - * e.g. trying to timeslice a pair of ordered contexts
> - */
> - if (!memcmp(execlists->active,
> - execlists->pending,
> - (port - execlists->pending) * sizeof(*port)))
> - goto skip_submit;
> -
> + /*
> + * We can skip poking the HW if we ended up with exactly the same set
> + * of requests as currently running, e.g. trying to timeslice a pair
> + * of ordered contexts.
> + */
> + if (submit &&
> + memcmp(execlists->active,
> + execlists->pending,
> + (port - execlists->pending) * sizeof(*port))) {
> *port = NULL;
> while (port-- != execlists->pending)
> execlists_schedule_in(*port, port - execlists->pending);
>
> - execlists->switch_priority_hint =
> - switch_prio(engine, *execlists->pending);
> -
> WRITE_ONCE(execlists->yield, -1);
> set_preempt_timeout(engine, *execlists->active);
> execlists_submit_ports(engine);
> } else {
> - start_timeslice(engine, execlists->queue_priority_hint);
> -skip_submit:
> ring_set_paused(engine, 0);
> while (port-- != execlists->pending)
> i915_request_put(*port);
> @@ -1979,8 +1944,6 @@ process_csb(struct intel_engine_cs *engine, struct i915_request **inactive)
> }
> } while (head != tail);
>
> - set_timeslice(engine);
> -
> /*
> * Gen11 has proven to fail wrt global observation point between
> * entry and tail update, failing on the ordering and thus
> @@ -1993,6 +1956,7 @@ process_csb(struct intel_engine_cs *engine, struct i915_request **inactive)
> * invalidation before.
> */
> invalidate_csb_entries(&buf[0], &buf[num_entries - 1]);
> + cancel_timer(&execlists->timer);
>
> return inactive;
> }
> @@ -2405,8 +2369,10 @@ static void execlists_submission_tasklet(unsigned long data)
> execlists_reset(engine, msg);
> }
>
> - if (!engine->execlists.pending[0])
> + if (!engine->execlists.pending[0]) {
> execlists_dequeue_irq(engine);
> + start_timeslice(engine);
> + }
>
> post_process_csb(post, inactive);
> rcu_read_unlock();
> @@ -3851,9 +3817,6 @@ void intel_execlists_show_requests(struct intel_engine_cs *engine,
> show_request(m, last, "\t\t", 0);
> }
>
> - if (execlists->switch_priority_hint != INT_MIN)
> - drm_printf(m, "\t\tSwitch priority hint: %d\n",
> - READ_ONCE(execlists->switch_priority_hint));
> if (execlists->queue_priority_hint != INT_MIN)
> drm_printf(m, "\t\tQueue priority hint: %d\n",
> READ_ONCE(execlists->queue_priority_hint));
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-01-06 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 12:39 [Intel-gfx] [PATCH 1/4] drm/i915/selftests: Break out of the lrc layout test after register mismatch Chris Wilson
2021-01-06 12:39 ` [Intel-gfx] [PATCH 2/4] drm/i915/selftests: Improve handling of iomem around stolen Chris Wilson
2021-01-06 15:12 ` Tvrtko Ursulin
2021-01-06 12:39 ` [Intel-gfx] [PATCH 3/4] drm/i915/gt: Restore ce->signal flush before releasing virtual engine Chris Wilson
2021-01-06 12:39 ` [Intel-gfx] [PATCH 4/4] drm/i915/gt: Remove timeslice suppression Chris Wilson
2021-01-06 15:57 ` Tvrtko Ursulin [this message]
2021-01-06 16:08 ` Chris Wilson
2021-01-06 16:19 ` Chris Wilson
2021-01-07 10:16 ` Tvrtko Ursulin
2021-01-07 10:27 ` Chris Wilson
2021-01-07 12:52 ` Tvrtko Ursulin
2021-01-06 13:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915/selftests: Break out of the lrc layout test after register mismatch Patchwork
2021-01-06 13:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-01-06 13:30 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-06 15:10 ` [Intel-gfx] [PATCH 1/4] " Tvrtko Ursulin
2021-01-06 15:17 ` Chris Wilson
2021-01-06 15:28 ` Tvrtko Ursulin
2021-01-06 16:38 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/4] " 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=0ed63aeb-d58e-5ec6-2072-65d17be612dc@linux.intel.com \
--to=tvrtko.ursulin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.