linux-kernel - Re: [PATCHSET v6] sched: Implement BPF extensible scheduler class

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: <CAPNVh5cn9N21jC9cbVfPbZQEQgT1MDn-N9R4RgZuvF9h3byhZA@mail.gmail.com>
Date: Mon, 24 Jun 2024 14:54:02 -0700
From: Peter Oskolkov <posk@...gle.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Tejun Heo <tj@...nel.org>, mingo@...hat.com, 
	peterz@...radead.org, juri.lelli@...hat.com, vincent.guittot@...aro.org, 
	dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com, 
	mgorman@...e.de, bristot@...hat.com, vschneid@...hat.com, ast@...nel.org, 
	daniel@...earbox.net, andrii@...nel.org, martin.lau@...nel.org, 
	joshdon@...gle.com, brho@...gle.com, pjt@...gle.com, derkling@...gle.com, 
	haoluo@...gle.com, dvernet@...a.com, dschatzberg@...a.com, 
	dskarlat@...cmu.edu, riel@...riel.com, changwoo@...lia.com, 
	himadrics@...ia.fr, memxor@...il.com, andrea.righi@...onical.com, 
	joel@...lfernandes.org, linux-kernel@...r.kernel.org, bpf@...r.kernel.org, 
	kernel-team@...a.com
Subject: Re: [PATCHSET v6] sched: Implement BPF extensible scheduler class

On Wed, Jun 19, 2024 at 7:35 PM Thomas Gleixner <tglx@...utronix.de> wrote:

[...]

> Just for the record, the scheduler people and myself spent a lot of time
> to help to get intrusive features like UMCG into mainline, but the
> efforts were dropped by the submitters for no reason. Short time after
> that sched_ext came around.

Hi Thomas,

I'm sorry I missed this callout re: UMCG last week.

The efforts were not dropped on our side, I assure you. For example, I
posted this last year:
https://lore.kernel.org/lkml/CAPNVh5eNEBu+gcex9pAej-_YN3zMKkG+rruXhopqS6EaG-izVQ@mail.gmail.com/T/
and I got no indication re: how I should proceed.

There were several earlier LKML posts that similarly did not result in
any actionable feedback. Based on this clear (maybe just perceived? if
so, I apologize) lack of interest in making UMCG ready for
upstream/mainline, we've decided to wait for sched_ext to get merged;
sched_ext already existed at the time, e.g.
https://lore.kernel.org/lkml/20221130082313.3241517-1-tj@kernel.org/.

I believe that sched_ext is flexible enough that, once merged, it will
allow us to build UMCG-like per-process schedulers on top of it, so I
see no reason in pushing both UMCG and sched_ext, given the difficulty
of getting anything merged. If I had to choose between UMCG and
sched_ext getting upstream (and I do not see both UMCG _and_ sched_ext
getting merged together any time soon), I'd choose sched_ext, because
it naturally opens up more opportunities to tailor scheduling to
different workloads.

Again, I appreciate the initial help and feedback you and Peter
provided re: UMCG; but then things stalled and I was not getting any
clear indication how to proceed; and given that UMCG can be built on
top of sched_ext (or ghost), and a clear (or perhaps also just
perceived) preference by sched maintainers to avoid competing
solutions, I now believe that sched_ext should be merged first.

Thanks,
Peter

[...]