LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Paul Menage <menage@google.com>
Cc: fedora-devel-list@redhat.com, opensuse-packaging@opensuse.org,
lkml <linux-kernel@vger.kernel.org>,
containers@lists.linux-foundation.org,
Balbir Singh <balbir@in.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>
Subject: Re: [RFC] libcg: design and plans
Date: Wed, 5 Mar 2008 16:37:31 +0530 [thread overview]
Message-ID: <20080305110730.GB22217@linux.vnet.ibm.com> (raw)
In-Reply-To: <6599ad830803050241k590e4389ud95b9b3ef920f8b6@mail.gmail.com>
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@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
next prev parent reply other threads:[~2008-03-05 11:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 15:23 Dhaval Giani
2008-03-04 17:15 ` Xpl++
2008-03-05 4:48 ` Balbir Singh
2008-03-05 5:26 ` Dhaval Giani
2008-03-05 11:56 ` Xpl++
2008-03-05 15:53 ` Dhaval Giani
2008-03-05 19:36 ` Xpl++
2008-03-04 18:05 ` Dave Hansen
2008-03-05 6:15 ` Paul Menage
2008-03-05 7:17 ` [Devel] " Denis V. Lunev
2008-03-05 11:48 ` Balbir Singh
2008-03-05 10:33 ` Dhaval Giani
2008-03-05 10:41 ` Paul Menage
2008-03-05 11:07 ` Dhaval Giani [this message]
2008-03-05 11:51 ` Paul Menage
2008-03-05 14:24 ` Balbir Singh
2008-03-05 18:55 ` Paul Menage
2008-03-20 22:04 ` Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080305110730.GB22217@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=balbir@in.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=fedora-devel-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=opensuse-packaging@opensuse.org \
--cc=skumar@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.com \
--subject='Re: [RFC] libcg: design and plans' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).