[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45A74557.4020004@in.ibm.com>
Date: Fri, 12 Jan 2007 13:52:47 +0530
From: Balbir Singh <balbir@...ibm.com>
To: Paul Menage <menage@...gle.com>
CC: vatsa@...ibm.com, sekharan@...ibm.com,
ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
xemul@...ru, rohitseth@...gle.com, pj@....com, mbligh@...gle.com,
winget@...gle.com, containers@...ts.osdl.org, serue@...ibm.com,
dev@...ru, devel@...nvz.org
Subject: Re: [ckrm-tech] [PATCH 3/6] containers: Add generic multi-subsystem
API to containers
Paul Menage wrote:
> On 1/11/07, Balbir Singh <balbir@...ibm.com> wrote:
>> to 0. To walk the hierarchy, I have no root now since I do not have
>> any task context. I was wondering if exporting the rootnode or providing
>> a function to export the rootnode of the mounter hierarchy will make
>> programming easier.
>
> Ah - I misunderstood what you were looking for before.
I'll try and post the changes to cpu_acct once I get the container system
working.
>
>> Something like
>>
>> struct container *get_root_container(struct container_subsys *ss)
>> {
>> return &rootnode[ss->hierarchy];
>> }
>
> Yes, something like that sounds fine - except that it would be
>
> return &rootnode[ss->hierarchy].top_container;
>
Aah! I missed the top_container bit. Do you want me to send you a patch for it?
It will be nice to have it in the next version.
> Paul
--
Balbir Singh,
Linux Technology Center,
IBM Software Labs
-
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