On Mon 16-06-14 10:12:33, Tejun Heo wrote: > On Mon, Jun 16, 2014 at 04:04:48PM +0200, Michal Hocko wrote: > > > For whatever reason, a user is stuck with thread-level granularity for > > > controllers which work that way, the user can use the old hierarchies > > > for them for the time being. > > > > So he can mount memcg with new cgroup API and others with old? > > Yes, you can read Documentation/cgroups/unified-hierarchy.txt for more > details. I think I cc'd you when posting unified hierarchy patchset, > didn't I? OK, I've obviously pushed that out of my brain, because you are really clear about it: " All controllers which are not bound to other hierarchies are automatically bound to unified hierarchy and show up at the root of it. Controllers which are enabled only in the root of unified hierarchy can be bound to other hierarchies at any time. This allows mixing unified hierarchy with the traditional multiple hierarchies in a fully backward compatible way. " This of course sorts out my concerns. Sorry about the noise! > > > Nope, some changes don't fit that model. CFTYPE_ON_ON_DFL is the > > > opposite. > > > > OK, I wasn't aware of this. On which branch I find this? > > They're all in the mainline now. git grep CFTYPE_ON_ON_DFL origin/master didn't show me anything. Thanks! -- Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>