From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Neel Natu <neelnatu@google.com>, Barret Rhoden <brho@google.com>,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
sched-ext@meta.com
Subject: Re: [PATCH sched_ext/for-6.15] sched_ext: Implement SCX_OPS_ALLOW_QUEUED_WAKEUP
Date: Thu, 13 Feb 2025 06:27:55 -1000 [thread overview]
Message-ID: <Z64di-4TaQ10GAbl@slm.duckdns.org> (raw)
In-Reply-To: <Z62q4Zuh7ry9tH3L@gpd3>
Hello,
On Thu, Feb 13, 2025 at 09:18:41AM +0100, Andrea Righi wrote:
> > Implement SCX_OPS_ALLOW_QUEUED_WAKEUP which allows BPF schedulers to choose
> > to enable ttwu_queue optimization.
>
> I'm wondering whether it makes sense to introduce a new SCX_OPS flag for
> this, considering that we already have the TTWU_QUEUE sched feature, that
> determines this behavior.
>
> Is this in perspective of a future scenario, when we may potentially have
> multiple scx schedulers running at the same time and they may want to set a
> different queued wakeup behavior?
It's more that it can be a breaking change for schedulers that expect
ops.select_cpu() to be called on wakeups. e.g. If we make this behavior the
default, scx_layered as of the last relesae would break in an unobvious but
serious way - it'd fail to occupy CPUs fully as it'd be skipping picking
idle CPU and pushing tasks there for a noticeable portion of wakeups on
multi-LLC machines. The same holds for most of the C schedulers.
Down the line, once everyone is onboard, we can maybe make it the default
and drop the flag but, for now, this needs to be opt-in.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-02-13 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 23:08 [PATCH sched_ext/for-6.15] sched_ext: Implement SCX_OPS_ALLOW_QUEUED_WAKEUP Tejun Heo
2025-02-13 8:18 ` Andrea Righi
2025-02-13 16:27 ` Tejun Heo [this message]
2025-02-13 16:30 ` Andrea Righi
2025-02-13 16:40 ` Tejun Heo
2025-02-13 17:13 ` Neel Natu
2025-02-13 17:33 ` [PATCH sched_ext/for-6.15 v2] " Tejun Heo
2025-02-14 7:00 ` Changwoo Min
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=Z64di-4TaQ10GAbl@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=brho@google.com \
--cc=changwoo@igalia.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neelnatu@google.com \
--cc=peterz@infradead.org \
--cc=sched-ext@meta.com \
--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