THat sort of accounting poses various horrible problems, which isOpenVZ assumes that tasks can't move between task-groups for a single reason:
user shouldn't be able to escape from the container.
But this have no implication on the design/implementation.
It does, for the memory controller at least. Things like shared
anon_vma's between tasks across containers make it somewhat harder.
It's much worse if you allow threads to split across containers.
we already have the code to account page fractions shared between containers.
Though, it is quite useless to do so for threads... Since this numbers have no meaning (not a real usage)
and only the sum of it will be a correct value.