Thread (31 messages) 31 messages, 4 authors, 2018-07-02

Re: [PATCH v10 2/9] cpuset: Add new v2 cpuset.sched.domain_root flag

From: Peter Zijlstra <peterz@infradead.org>
Date: 2018-06-21 09:20:33
Also in: linux-doc, lkml

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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help