From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET sched_ext/for-6.15] sched_ext: Enhance built-in idle selection with preferred CPUs
Date: Thu, 6 Mar 2025 20:02:33 +0100 [thread overview]
Message-ID: <Z8nxSUEfREpQjRXo@gpd3> (raw)
In-Reply-To: <Z8nwU3C-WiWN7eia@slm.duckdns.org>
On Thu, Mar 06, 2025 at 08:58:27AM -1000, Tejun Heo wrote:
> On Thu, Mar 06, 2025 at 07:54:34PM +0100, Andrea Righi wrote:
> > Just to make sure I understand, you mean provide two separate kfuncs:
> > scx_bpf_select_cpu_and() and scx_bpf_select_cpu_pref(), instead of
> > introducing the flag?
>
> Oh I meant just having scx_bpf_select_cpu_and(). The caller can just call it
> twice for _pref() behavior, right?
Oh I see, you call it for the pref CPUs first and then for all the CPUs to
get the same behavior (similar to what we do with the SMT idle cores).
Yeah, that can work. Good idea!
Thanks,
-Andrea
next prev parent reply other threads:[~2025-03-06 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 18:18 [PATCHSET sched_ext/for-6.15] sched_ext: Enhance built-in idle selection with preferred CPUs Andrea Righi
2025-03-06 18:18 ` [PATCH 1/4] sched_ext: idle: Honor idle flags in the built-in idle selection policy Andrea Righi
2025-03-06 18:18 ` [PATCH 2/4] sched_ext: idle: Introduce the concept of preferred CPUs Andrea Righi
2025-03-06 18:18 ` [PATCH 3/4] sched_ext: idle: Introduce scx_bpf_select_cpu_pref() Andrea Righi
2025-03-07 3:15 ` Changwoo Min
2025-03-07 6:35 ` Andrea Righi
2025-03-06 18:18 ` [PATCH 4/4] selftests/sched_ext: Add test for scx_bpf_select_cpu_pref() Andrea Righi
2025-03-06 18:34 ` [PATCHSET sched_ext/for-6.15] sched_ext: Enhance built-in idle selection with preferred CPUs Tejun Heo
2025-03-06 18:54 ` Andrea Righi
2025-03-06 18:58 ` Tejun Heo
2025-03-06 19:02 ` Andrea Righi [this message]
2025-03-07 3:14 ` 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=Z8nxSUEfREpQjRXo@gpd3 \
--to=arighi@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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