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 12:34:28 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2010121232410.2901@hadrien> (raw)
In-Reply-To: <CAKfTPtCPapkwS7B5X3XQsQFx7GXa-RSzRWO1e6n5JzLT7nTvrA@mail.gmail.com>
> > 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?
julia
next prev parent reply other threads:[~2020-10-12 10:34 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 ` Julia Lawall [this message]
2020-10-12 11:09 ` SD_LOAD_BALANCE Vincent Guittot
2020-10-12 11:18 ` SD_LOAD_BALANCE Julia Lawall
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.2010121232410.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®