It was me who hacked Alan's beancounter code.
I've finished the generic interface for beancounter management
and mostly implemented the accounting for virtual memory
and unpageable kernel memory occupied by groups of tasks.
As unpageable kernel memory the code currently
accounts task+stack structures, mlock()ed memory and page
directories. Socket buffer space and other accounting aren't
implemented yet.
I plan to finish the patch when I'll have more free time (probably
at the beginning of November).
>
> The model SCO use for a user is fairly simple. There are three uid values
> involved - uid, euid, and luid. The luid is a login uid. It is set once and
> cannot be changed.
>
> The code I had was less restrictive than the SCO idea - you have an luid
> which sets your current->beancounter. That is the beancounter to which all
> your resources get charged. Each resource object you allocate also makes
> a copy by reference counting of the bean counter so that it can free up
> the resources on an object.
Best wishes
Andrey V.
Savochkin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/