[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YGxtLOxCb4LO8kN0@slm.duckdns.org>
Date: Tue, 6 Apr 2021 10:16:12 -0400
From: Tejun Heo <tj@...nel.org>
To: Joel Fernandes <joel@...lfernandes.org>
Cc: Hao Luo <haoluo@...gle.com>, Peter Zijlstra <peterz@...radead.org>,
"Hyser,Chris" <chris.hyser@...cle.com>,
Josh Don <joshdon@...gle.com>, Ingo Molnar <mingo@...nel.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Valentin Schneider <valentin.schneider@....com>,
Mel Gorman <mgorman@...e.de>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Glexiner <tglx@...utronix.de>,
Michal Koutný <mkoutny@...e.com>,
Christian Brauner <christian.brauner@...ntu.com>,
Zefan Li <lizefan.x@...edance.com>
Subject: Re: [PATCH 0/9] sched: Core scheduling interfaces
Hello,
On Mon, Apr 05, 2021 at 02:46:09PM -0400, Joel Fernandes wrote:
> Yeah, its at http://lore.kernel.org/r/20200822030155.GA414063@google.com
> as mentioned above, let me know if you need any more details about
> usecase.
Except for the unspecified reason in usecase 4, I don't see why cgroup is in
the picture at all. This doesn't really have much to do with hierarchical
resource distribution. Besides, yes, you can use cgroup for logical
structuring and identificaiton purposes but in those cases the interactions
and interface should be with the original subsystem while using cgroup IDs
or paths as parameters - see tracing and bpf for examples.
Thanks.
--
tejun
Powered by blists - more mailing lists