From: Julia Lawall <julia.lawall@inria.fr>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Valentin Schneider <valentin.schneider@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Gilles Muller <Gilles.Muller@inria.fr>
Subject: Re: SD_LOAD_BALANCE
Date: Mon, 12 Oct 2020 13:18:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2010121317470.2901@hadrien> (raw)
In-Reply-To: <CAKfTPtDqKqoLg9OOYMy5bVVnQKGNb3Z9hL6tWaxqKzv2+NdFXw@mail.gmail.com>
On Mon, 12 Oct 2020, Vincent Guittot wrote:
> On Mon, 12 Oct 2020 at 12:34, Julia Lawall <julia.lawall@inria.fr> wrote:
> >
> > > > Would it be useful to always check whether prev is idle, perhaps in
> > > > wake_affine_idle or perhaps in select_idle_sibling?
> > >
> > > Yes, that would make sense to add a condition in wake_affine_idle to
> > > return prev if this cpu is not idle (or about to become idle)
> >
> > The case where this cpu is idle would be in the interrupt case. If both
> > prev cpu and this cpu are idle, is it more desirable to move the thread to
> > this cpu or to leave it where it was?
>
> I think that we should keep the current behavior regarding this cpu
> and the shared cache case and add one more test before the last return
> of the function.
>
> right now, we select this_cpu:
> -if this cpu is idle, it shares cache with prev and previous is not idle.
> -if it's a sync wake up because we expect the task to use local data
> of the current running task on this cpu.
>
> Then we add a new case to return prev cpu if it is idle which is your case
OK, sounds good, thanks.
julia
next prev parent reply other threads:[~2020-10-12 11:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 14:09 SD_LOAD_BALANCE Julia Lawall
2020-09-03 16:59 ` SD_LOAD_BALANCE Valentin Schneider
2020-09-03 17:10 ` SD_LOAD_BALANCE Julia Lawall
2020-09-03 18:17 ` SD_LOAD_BALANCE Julia Lawall
2020-10-10 16:14 ` SD_LOAD_BALANCE Julia Lawall
2020-10-12 10:16 ` SD_LOAD_BALANCE Vincent Guittot
2020-10-12 10:34 ` SD_LOAD_BALANCE Julia Lawall
2020-10-12 11:09 ` SD_LOAD_BALANCE Vincent Guittot
2020-10-12 11:18 ` Julia Lawall [this message]
2020-10-12 11:21 ` SD_LOAD_BALANCE Peter Zijlstra
2020-10-12 11:31 ` SD_LOAD_BALANCE Julia Lawall
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=alpine.DEB.2.22.394.2010121317470.2901@hadrien \
--to=julia.lawall@inria.fr \
--cc=Gilles.Muller@inria.fr \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®