Hello, On Wed, Sep 05, 2012 at 01:31:56PM +0400, Glauber Costa wrote: > > I simply don't want to have to do two (or more) hierarchy walks for > > accounting on every schedule event, all that pointer chasing is stupidly > > expensive. > > You wouldn't have to do more than one hierarchy walks for that. What > Tejun seems to want, is the ability to not have a particular controller > at some point in the tree. But if they exist, they are always together.
Nope, as I wrote in the other reply, for cpu and cpuacct, either just merge them or kill cpuacct if you want to avoid silliness from walking multiple times. Does cpuset cause problem in this regard too? Or can it be handled similarly to other controllers? I think the confusion here is that we're talking about two different issues. As for cpuacct, I can see why strict co-mounting can be attractive but then again if that's gonna be required, there's no point in having them separate, right? If that's the way you want it, just trigger WARN_ON() if cpu and cpuacct aren't co-mounted and later on kill cpuacct. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
