[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830803050241k590e4389ud95b9b3ef920f8b6@mail.gmail.com>
Date: Wed, 5 Mar 2008 02:41:41 -0800
From: "Paul Menage" <menage@...gle.com>
To: "Dhaval Giani" <dhaval@...ux.vnet.ibm.com>
Cc: fedora-devel-list@...hat.com, opensuse-packaging@...nsuse.org,
lkml <linux-kernel@...r.kernel.org>,
containers@...ts.linux-foundation.org,
"Balbir Singh" <balbir@...ibm.com>,
"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
"Srivatsa Vaddagiri" <vatsa@...ux.vnet.ibm.com>,
"Sudhir Kumar" <skumar@...ux.vnet.ibm.com>
Subject: Re: [RFC] libcg: design and plans
On Wed, Mar 5, 2008 at 2:33 AM, Dhaval Giani <dhaval@...ux.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
Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists