On 10/1/07, Serge E. Hallyn <serue@xxxxxxxxxx> wrote: > I'd advocate following this path. Have you started any > patches for this? Started playing with it, but only really to see what breaks so far. > > - the guest can only see subsystems in the same hierarchy, which > > same hierarchy as the virtualization cgroup subsystem, right? Right. > > So then for subsystems which the guest did select, are there > default values inherited from the parent cgroup, and restrictions based > on those? Or does the guest get to set any values it wants for those > subsystems? That's something that's going to need to be subsystem-specific, I think. For something like cpusets, that already handles restricting a child to be a subset of a parent, this should be automatic. There's already talk of adding hierarchy to resource counters, which would theoretically solve the problem for all resource counter users. Paul _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
