linux-kernel - Re: [PATCHSET sched_ext/for-6.15] sched_ext: Enhance built-in idle selection with preferred CPUs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z8nxSUEfREpQjRXo@gpd3>
Date: Thu, 6 Mar 2025 20:02:33 +0100
From: Andrea Righi <arighi@...dia.com>
To: Tejun Heo <tj@...nel.org>
Cc: David Vernet <void@...ifault.com>, Changwoo Min <changwoo@...lia.com>,
	bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHSET sched_ext/for-6.15] sched_ext: Enhance built-in idle
 selection with preferred CPUs

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