[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <44E98BA5.8010605@sw.ru>
Date: Mon, 21 Aug 2006 14:32:05 +0400
From: Kirill Korotaev <dev@...ru>
To: sekharan@...ibm.com
CC: Rik van Riel <riel@...hat.com>, ckrm-tech@...ts.sourceforge.net,
Andi Kleen <ak@...e.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Christoph Hellwig <hch@...radead.org>,
Andrey Savochkin <saw@...ru>,
Alan Cox <alan@...rguk.ukuu.org.uk>, hugh@...itas.com,
Ingo Molnar <mingo@...e.hu>, devel@...nvz.org,
Pavel Emelianov <xemul@...nvz.org>
Subject: Re: [ckrm-tech] [RFC][PATCH 3/7] UBC: ub context and inheritance
Chandra Seetharaman wrote:
> On Wed, 2006-08-16 at 19:38 +0400, Kirill Korotaev wrote:
>
>>Contains code responsible for setting UB on task,
>>it's inheriting and setting host context in interrupts.
>>
>>Task references three beancounters:
>> 1. exec_ub current context. all resources are
>> charged to this beancounter.
>> 2. task_ub beancounter to which task_struct is
>> charged itself.
>
>
> I do not see why task_ub is needed ? i do not see it being used
> anywhere.
it is used to charge task itself. will be heavily used in next patch set
adding "numproc" UBC parameter.
>> 3. fork_sub beancounter which is inherited by
>> task's children on fork
>
>
>>>From other emails it looks like renaming fork/exec to be real/effective
> will be easier to understand.
there is no "real". exec_ub is effective indeed,
but fork_sub is the one to inherit on fork().
Kirill
-
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