[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830704031030n2311bcd7hca9f34e64c66337f@mail.gmail.com>
Date: Tue, 3 Apr 2007 10:30:28 -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,
containers@...ts.osdl.org, pj@....com,
"Eric W. Biederman" <ebiederm@...ssion.com>, mbligh@...gle.com,
winget@...gle.com, rohitseth@...gle.com,
"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:
>
> Hmm no .. I currently have nsproxy having just M additional pointers, where
> M is the maximum number of resource controllers and a single dentry
> pointer.
So how do you implement something like the /proc/<PID>/container info
file in my patches? (Or more generally, tell which container a task is
in for a given hierarchy?)
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