[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 12 Dec 2022 08:06:55 -1000
From: Tejun Heo <tj@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: torvalds@...ux-foundation.org, mingo@...hat.com,
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, linux-kernel@...r.kernel.org,
bpf@...r.kernel.org, kernel-team@...a.com
Subject: Re: [PATCH 10/31] sched: Add @reason to
sched_class->rq_{on|off}line()
On Mon, Dec 12, 2022 at 12:57:36PM +0100, Peter Zijlstra wrote:
> On Tue, Nov 29, 2022 at 10:22:52PM -1000, Tejun Heo wrote:
> > ->rq_{on|off}line are called either during CPU hotplug or cpuset partition
> > updates. Let's add an argument to distinguish the two cases. The argument
> > will be used by a new sched_class to track CPU hotplug events.
>
> Again, utter lack of why.
sched_ext wants to tell the BPF scheduler about CPU hotplugs in a way that's
synchronized with rq state changes, so it needs to distinguish the two
cases. Will update the description.
Thanks.
--
tejun
Powered by blists - more mailing lists