Re: [PATCH v2 14/14] Change CPUACCT to default n

[Peter Zijlstra]

On Thu, 2011-11-24 at 14:38 -0200, Glauber Costa wrote:
> It's hard for me to say that, since I come from a virtualization 
> background: for us, a single cgroup would do just fine: even the 
> division between mem and cpu is not needed. However, I've been learning 
> recently that the use cases for that are quite diverse. So I'll have to 
> leave the answer to Balbir, and other interested parties. 

Hehe, I'm the one running a CGROUP=n kernel, so what do I know. Its just
that all this stuff hurts my brain.

Maybe we should just add functionality that requires controllers to be
co-mounted and this extra functionality will then make people co-mount
since you know features.. :-)

I know I've wanted to do that several times, so far I've always resisted
because it looked like pain, but hey, if I can cause more pain somewhere
else and my life gets easier in the long run I might change my mind ;-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/