On Fri, Mar 27, 2015 at 03:26:48PM +0100, Michal Privoznik wrote: > The heart of the patchset are the last two patches. Long story > short, if a domain is configured to be pinned onto a set of NUMA > nodes stricly, we use both CGroups and numa_set_membind(). While > we can change the former later on a user's wish, we can't change > the latter. Therefore, any subsequent memory enlargement (e.g. > via virsh setmem $dom) will result in memory still being > allocated from old NUMA nodes and OOM killer interference is > likely to occur. > > Michal Privoznik (6): > virCgroupNewPartition: Fix comment > virCgroupNew: Enhance debug message > virCgroupController: Check the enum fits into 'int' > qemuDomainGetNumaParameters: Check for the correct CGroup controller > qemuProcessHook: Call virNuma*() iff needed > virLXCControllerSetupResourceLimits: Call virNuma*() iff needed >
ACK to patches 1-4, safe during the freeze. Jan
signature.asc
Description: Digital signature
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
