Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Namespaces in operation, part 1: namespaces overview
Posted Jan 4, 2013 20:47 UTC (Fri) by ebiederm (subscriber, #35028)
Posted Jan 4, 2013 22:58 UTC (Fri) by Cyberax (✭ supporter ✭, #52523)
Posted Jan 5, 2013 6:39 UTC (Sat) by ebiederm (subscriber, #35028)
As for taking a slice of a control group hierarchy and making it visible in a container the best practical solution I have heard is to do a "mount --bind" of a slice of that hierarchy into a container. Something better was promised at the time control groups were merged but that has never appeared.
The design mistake of embedding a view of the system packed with global identifiers and silly unwarranted assumptions into a filesystem seems to be an easy mistake to make and is very annoying to deal with.
From what little time I have had to look at the control group interface to user space, and the control group model of controlling resources, and the direction all of that is evolving I really don't like the result. Still today control groups are the best solution we have in linux today to the recursive resource limiting problem.
I encourage people who care to help by looking at control groups, reporting bugs and usability problems, and even better writing and submitting patches.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds