[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1457922201.3680.44.camel@gmail.com>
Date: Mon, 14 Mar 2016 03:23:21 +0100
From: Mike Galbraith <umgwanakikbuti@...il.com>
To: Tejun Heo <tj@...nel.org>
Cc: torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
a.p.zijlstra@...llo.nl, mingo@...hat.com, lizefan@...wei.com,
hannes@...xchg.org, pjt@...gle.com, linux-kernel@...r.kernel.org,
cgroups@...r.kernel.org, linux-api@...r.kernel.org,
kernel-team@...com
Subject: Re: [PATCHSET RFC cgroup/for-4.6] cgroup, sched: implement resource
group and PRIO_RGRP
On Sun, 2016-03-13 at 11:00 -0400, Tejun Heo wrote:
> There can be use cases where building cpu resource hierarchy which is
> completely alien to how the rest of the system is organized is useful.
Well, from my POV it's the "process" oriented thingy that's the alien,
and one that wants to meet an alien juice resistant shovel ;-)
Another example is cpusets. I use it, and I know beyond doubt that my
employer's customers use it for RT/HPC purposes out in the wild, and
that very much includes placing critical _threads_ in exclusive sets.
-Mike
Powered by blists - more mailing lists