From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <andrea.righi@linux.dev>
Cc: David Vernet <void@manifault.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched_ext: improve WAKE_SYNC behavior for default idle CPU selection
Date: Fri, 18 Oct 2024 10:26:38 -1000 [thread overview]
Message-ID: <ZxLEfqsZJH6Mp1Fd@slm.duckdns.org> (raw)
In-Reply-To: <20241018180951.599625-1-andrea.righi@linux.dev>
On Fri, Oct 18, 2024 at 08:09:51PM +0200, Andrea Righi wrote:
> In the sched_ext built-in idle CPU selection logic, when handling a
> WF_SYNC wakeup, we always attempt to migrate the task to the waker's
> CPU, as the waker is expected to yield the CPU after waking the task.
>
> However, it may be preferable to keep the task on its previous CPU if
> the waker's CPU is cache-affine.
>
> The same approach is also used by the fair class and in other scx
> schedulers, like scx_rusty and scx_bpfland.
>
> Therefore, apply the same logic to the built-in idle CPU selection
> policy as well.
>
> Signed-off-by: Andrea Righi <andrea.righi@linux.dev>
Applied to sched_ext/for-6.13.
Thanks.
--
tejun
prev parent reply other threads:[~2024-10-18 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 18:09 [PATCH v2] sched_ext: improve WAKE_SYNC behavior for default idle CPU selection Andrea Righi
2024-10-18 20:26 ` Tejun Heo [this message]
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=ZxLEfqsZJH6Mp1Fd@slm.duckdns.org \
--to=tj@kernel.org \
--cc=andrea.righi@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=void@manifault.com \
/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