linux-kernel - Re: [PATCH] sched_ext: Provide a sysfs enable

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: <ZvGfAqVgbB_p4SKX@slm.duckdns.org>
Date: Mon, 23 Sep 2024 07:01:54 -1000
From: Tejun Heo <tj@...nel.org>
To: Phil Auld <pauld@...hat.com>
Cc: Andrea Righi <andrea.righi@...ux.dev>,
	David Vernet <void@...ifault.com>,
	Giovanni Gherdovich <giovanni.gherdovich@...e.com>,
	Kleber Sacilotto de Souza <kleber.souza@...onical.com>,
	Marcelo Henrique Cerri <marcelo.cerri@...onical.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched_ext: Provide a sysfs enable_seq counter

Hello,

On Mon, Sep 23, 2024 at 12:57:49PM -0400, Phil Auld wrote:
..
> > I'll apply as-is. Let's add per-scheduler load seq separately.
> 
> Thanks! I was thinking that per-scheduler you could just snapshot the
> global counter (either before or after increment) on load. Then you
> could easily tell when each was loaded relative to each other etc.

Yeap.

> Especially while "per-scheduler" is defined by string comparison I'd
> prefer not to rely on that for this use case. 

Thanks.

-- 
tejun