[Workman-devel] cgroup: status-quo and userland efforts
vgoyal at redhat.com
Mon Apr 8 19:46:31 UTC 2013
On Mon, Apr 08, 2013 at 12:20:24PM -0700, Tejun Heo wrote:
> > For example, one might want to say that maximum IO bandwidth for
> > virtual machine virt1 on disk sda should be 10MB/s. Now libvirt
> > should be able to save it in virtual machine specific configuration
> > easily and whenever virtual machine is started, create a children
> > cgroup, set the limits as specified.
> Yes, sure, libvirt can *request* whatever it seems appropriate to the
> central authority, which will decide whether it'll be able to honor
> the request and grant it if possible and allowed by policies in
10MB/s is an absolute limit. So I guess there is nothing to be requested
from an central authority here in terms of resources.
Even in the case of IO weight or cpu shares, there is nothing to be asked
from central authority. Well, there is. Creation of new croups changes
effective %share of peer groups. More below.
Where it makes sense though is if one says give a particular service
25% cpu. Then suddenly all the peer and parent entities become important.
IIUC, initial draft of workman does not address this issue.
It would be good to think more about it. How a user can ensure minimum
resources to a partition/service. Because in that case at every level
somebody needs to keep track how much of resources have been committed
as minimum requirements and more consumers can't be allowed at same level.
(This sounds like cpu RT time division among various cgroups).
More information about the Containers