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] [day] [month] [year] [list]
Message-ID: <ZxLEfqsZJH6Mp1Fd@slm.duckdns.org>
Date: Fri, 18 Oct 2024 10:26:38 -1000
From: Tejun Heo <tj@...nel.org>
To: Andrea Righi <andrea.righi@...ux.dev>
Cc: David Vernet <void@...ifault.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] sched_ext: improve WAKE_SYNC behavior for default
 idle CPU selection

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@...ux.dev>

Applied to sched_ext/for-6.13.

Thanks.

-- 
tejun

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ