[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830704031049v7fad0a83q3c24211cf44d71d6@mail.gmail.com>
Date: Tue, 3 Apr 2007 10:49:49 -0700
From: "Paul Menage" <menage@...gle.com>
To: vatsa@...ibm.com
Cc: sekharan@...ibm.com, ckrm-tech@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, xemul@...ru, rohitseth@...gle.com,
pj@....com, "Eric W. Biederman" <ebiederm@...ssion.com>,
mbligh@...gle.com, winget@...gle.com, containers@...ts.osdl.org,
"Serge E. Hallyn" <serue@...ibm.com>, dev@...ru, devel@...nvz.org
Subject: Re: [ckrm-tech] [PATCH 7/7] containers (V7): Container interface to nsproxy subsystem
On 4/3/07, Srivatsa Vaddagiri <vatsa@...ibm.com> wrote:
> > (Or more generally, tell which container a task is
> > in for a given hierarchy?)
>
> Why is the hierarchy bit important here? Usually controllers need to
> know "tell me what cpuset this task belongs to", which is answered
> by tsk->nsproxy->ctlr_data[CPUSET_ID].
I was thinking of queries from userspace.
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