>>Sorry, I did not get what you mean? I simply translate 
>>
>># cat /etc/pve/lxc/101/config 
l>>xc.cgroup.cpu.cfs_period_us = 100000 
>>lxc.cgroup.cpu.cfs_quota_us = 100000 
>>
>># pct config 101 
>>cpus: 1 



>>You think I should call it 'cpulimit' instead of 'cpus'? 

I mean, if you go in a container, do a "top", you'll always see the full number 
of cpus of the host.

in openvz :
 cfs_quota_us = cpulimit.
 cpus = number of cores assign in a container.


It's possible to really fix the number of cpus inside the container with 
cpu.cpuset.
(The only problem is that we need to specify cpuids we want to assign, so it's 
not easy to have a good auto loadbalacing with multiple containers)


----- Mail original -----
De: "dietmar" <diet...@proxmox.com>
À: "aderumier" <aderum...@odiso.com>
Cc: "pve-devel" <pve-devel@pve.proxmox.com>
Envoyé: Vendredi 29 Mai 2015 12:51:00
Objet: Re: [pve-devel] qemu-server : cgroups implementation through systemd-run

> >>Great. I guess we can also hotplug that? 
> 
> Yes sure. it's just a write in /sys/fs/cgroups. 
> 
> This could be done online too in lxc. 

OK 

> BTW, I see that in lxc gui, the cpus number field = 
> lxc.cgroup.cpu.cfs_quota_us, so it's more cpulimit. 
> (all cores are present in container) 

Sorry, I did not get what you mean? I simply translate 

# cat /etc/pve/lxc/101/config 
lxc.cgroup.cpu.cfs_period_us = 100000 
lxc.cgroup.cpu.cfs_quota_us = 100000 

# pct config 101 
cpus: 1 

You think I should call it 'cpulimit' instead of 'cpus'? 


l 
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Reply via email to