[RFC] libcg: design and plans

[Dhaval Giani]

On Wed, Mar 05, 2008 at 02:41:41AM -0800, Paul Menage wrote:
> On Wed, Mar 5, 2008 at 2:33 AM, Dhaval Giani <dhaval at linux.vnet.ibm.com> wrote:
> >
> >  So there are two different points, /mem and /cpu. /mem has A and C and
> >  /cpu has A, B and C. A and B of /cpu correspond to A of /mem and the C's
> >  are the same. With this is mind, if I say a task should move to B in
> >  /cpu, it should also move to A in /mem?
> >
> 
> Maybe clearer to say that /mem has two cgroups, AB and C. The
> abstraction provided by libcg would be of three groups, A, B and C.
> Asking libcg to move a process to abstract group B would result it
> moving to /mem/AB and /cpu/B
> 

OK. Hmm, I've not really thought about it. At first thought, it should
not be very difficult. Only thing I am not sure is the arbitrary
grouping of the groups (ok, a bit confusing). If that information is
maintained somewhere, it should be pretty straightforward. (Only thing
is that I am not sure how it will be done, and where the grouping
information should be stored. configuration looks like the logical
place, but I am not sure)

Thanks,
-- 
regards,
Dhaval