[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZneBqla93mBpGdH0@slm.duckdns.org>
Date: Sat, 22 Jun 2024 16:00:10 -1000
From: Tejun Heo <tj@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, 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
Hello,
On Fri, Jun 21, 2024 at 09:34:22AM -0700, Linus Torvalds wrote:
> (b) the for_each_active_class() thing that I think would actually be
> better off just being done explicitly in sched/core.c, but probably
> only makes sense after integration
Just posted a patchset to integrate sched_ext a bit better. I open coded
for_balance_class_range() and moved for_each_active_class() and friends to
kernel/sched/sched.h. If something else would look better, please let me
know.
http://lkml.kernel.org/r/20240623015057.3383223-1-tj@kernel.org
Thanks.
--
tejun
Powered by blists - more mailing lists