[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] cgroup memoryinfo handling



On 03/24/2011 04:09 PM, Zvi Dubitzky wrote:
> As per the 'virsh memtune'   how are the items :hard_limit,  soft_limit, 
> min_guarantee  mapped  to the items mentioned in RedHat 'Resource 
> Manangement Guide' , such as  : memory.limit_in_bytes    etc.

Specific support questions are probably best asked through Red Hat
support channels.  But the documentation currently states this:

http://libvirt.org/formatdomain.html#elementsResources

hard_limit
    The optional hard_limit element is the maximum memory the guest can
use. The units for this value are kilobytes (i.e. blocks of 1024 bytes)
soft_limit
    The optional soft_limit element is the memory limit to enforce
during memory contention. The units for this value are kilobytes (i.e.
blocks of 1024 bytes)
swap_hard_limit
    The optional swap_hard_limit element is the maximum memory plus swap
the guest can use. The units for this value are kilobytes (i.e. blocks
of 1024 bytes). This has to be more than hard_limit value provided
min_guarantee
    The optional min_guarantee element is the guaranteed minimum memory
allocation for the guest. The units for this value are kilobytes (i.e.
blocks of 1024 bytes)

which should be pretty easy to map up to the corresponding cgroup
controller file names like memory.limit_in_bytes.  You can also browse
the file src/util/cgroups.c to see which particular cgroup files are
used for each limit.

If you have ideas for improving the documentation, patches are welcome.

-- 
Eric Blake   eblake redhat com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]