Re: [RFC, PATCH 0/5] Going forward with Resource Management - A cpucontroller

From: Martin J. Bligh
Date: Mon Aug 07 2006 - 10:32:33 EST

Kirill Korotaev wrote:

OpenVZ 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.

THat sort of accounting poses various horrible problems, which is
why we steered away from it. If you share pages between containers
(presumably billing them equal shares per user), what happens
when you're already at your limit, and one of your sharer's exits?

Plus, are you billing by vma or address_space?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at