Messages in this thread | | | Date | Thu, 21 Jun 2018 11:20:13 +0200 | From | Peter Zijlstra <> | Subject | Re: [PATCH v10 2/9] cpuset: Add new v2 cpuset.sched.domain_root flag |
| |
On Thu, Jun 21, 2018 at 03:58:06PM +0800, Waiman Long wrote:
> As for the inconsistency between the real root and the container root, > this is true for almost all the controllers. So it is a generic problem. > One possible solution is to create a kind a pseudo root cgroup for the > container that looks and feels like a real root. But is there really a > need to do that?
I don't really know. I thought the idea was to make containers indistinguishable from a real system. Now I know we're really rather far away from that in reality, and I really have no clue how important all that is.
It all depends on how exactly this works; is it like I assumed, that this file is owned by the parent instead of the current directory? And that if you namespace this, you have an effective read-only file?
Then fixing the inconsistency is trivial; simply provide a read-only file for the actual root cgroup too.
And if the solution is trivial, I don't see a good reason not to do it.
| |