On Wed, 2006-08-16 at 19:38 +0400, Kirill Korotaev wrote:it is used to charge task itself. will be heavily used in next patch set
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.
there is no "real". exec_ub is effective indeed,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/effectivewill be easier to understand.