All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nayan Deshmukh <nayan26deshmukh@gmail.com>
To: "Christian König" <Christian.Koenig@amd.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/scheduler: use hw_rq_count for load calculation
Date: Tue, 23 Oct 2018 23:52:56 +0900	[thread overview]
Message-ID: <CAFd4ddyZu=Brpsu-9RbT3Tgev5hWq+-xKOR_phBVn-nHJ_d9Pw@mail.gmail.com> (raw)
In-Reply-To: <dbad051b-9634-f317-1712-15b677544ada@amd.com>

On Mon, Oct 22, 2018 at 9:46 PM Koenig, Christian
<Christian.Koenig@amd.com> wrote:
>
> Am 18.10.18 um 17:37 schrieb :
> > If the hardware queue for a scheduler is empty then we don't
> > need to the shift the entities from their current scheduler
> > as they are not getting scheduled because of some dependency.
>
> That is most likely not a good idea. The scheduler might not have
> anything todo right now, but we can't guarantee that it will stay this way.
>
I agree. But conversely it might also happens that one hardware engine
is sitting idle until the runqueue of the other schedulers comes to
the level of this scheduler.

I think the best option is to pick the scheduler with empty hardware
queue when the difference in their software queues is less that
MAX_DIFF. The problem is that determining the optimal value of
MAX_DIFF is not all that easy.

For now it's better to use MAX_DIFF=0 as you suggested until we can
find a way to determine its value.

Regards,
Nayan
> Instead when the number of jobs on a rq is identical we should select
> the one with the least entities on it.
>
> This should make sure that we distribute the entities equally among the
> runqueues even when they are idle.
>
> Christian.
>
> >
> > Signed-off-by: Nayan Deshmukh <nayan26deshmukh@gmail.com>
> > ---
> >   drivers/gpu/drm/scheduler/sched_entity.c | 14 ++++++++++++++
> >   1 file changed, 14 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/scheduler/sched_entity.c b/drivers/gpu/drm/scheduler/sched_entity.c
> > index 3e22a54a99c2..4d18497d6ecf 100644
> > --- a/drivers/gpu/drm/scheduler/sched_entity.c
> > +++ b/drivers/gpu/drm/scheduler/sched_entity.c
> > @@ -130,6 +130,12 @@ drm_sched_entity_get_free_sched(struct drm_sched_entity *entity)
> >       int i;
> >
> >       for (i = 0; i < entity->num_rq_list; ++i) {
> > +             if (atomic_read(&entity->rq_list[i]->sched->hw_rq_count) <
> > +                     entity->rq_list[i]->sched->hw_submission_limit) {
> > +                     rq = entity->rq_list[i];
> > +                     break;
> > +             }
> > +
> >               num_jobs = atomic_read(&entity->rq_list[i]->sched->num_jobs);
> >               if (num_jobs < min_jobs) {
> >                       min_jobs = num_jobs;
> > @@ -470,6 +476,14 @@ void drm_sched_entity_select_rq(struct drm_sched_entity *entity)
> >       if (spsc_queue_count(&entity->job_queue) || entity->num_rq_list <= 1)
> >               return;
> >
> > +     /*
> > +      * We don't need to shift entity if the hardware
> > +      * queue of current scheduler is empty
> > +      */
> > +     if (atomic_read(&entity->rq->sched->hw_rq_count) <
> > +             entity->rq->sched->hw_submission_limit)
> > +             return;
> > +
> >       fence = READ_ONCE(entity->last_scheduled);
> >       if (fence && !dma_fence_is_signaled(fence))
> >               return;
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-10-23 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 15:37 [PATCH] drm/scheduler: use hw_rq_count for load calculation Nayan Deshmukh
2018-10-22 12:46 ` Koenig, Christian
2018-10-23 14:52   ` Nayan Deshmukh [this message]
2018-10-28  9:59     ` [PATCH v2] " Nayan Deshmukh
2018-11-07  8:09       ` Christian König

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='CAFd4ddyZu=Brpsu-9RbT3Tgev5hWq+-xKOR_phBVn-nHJ_d9Pw@mail.gmail.com' \
    --to=nayan26deshmukh@gmail.com \
    --cc=Christian.Koenig@amd.com \
    --cc=dri-devel@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.