search for: memnode

...nodeset="0-7"/> </numatune> However, this is not enough. This XML pins only vCPUs and not guest memory. So while say vCPU #0 is pinned onto physical CPU #0, the memory for guest NUMA #0 might be allocated at host NUMA #7 (for instance). You need to add: <numatune> <memnode cellid="0" mode="strict" nodeset="0"/> <memnode cellid="1" mode="strict" nodeset="1"/> ... </numatune> This will ensure also the guest memory pinning. But wait, there is more. In your later e-mails you mention slow disk...

...7' cpuset='27' /><vcpupin vcpu='28' cpuset='28' /><vcpupin vcpu='29' cpuset='29' /><vcpupin vcpu='30' cpuset='30' /><vcpupin vcpu='31' cpuset='31' /></cputune> > <numatune> > <memnode cellid="0" mode="strict" nodeset="0"/> > <memnode cellid="1" mode="strict" nodeset="1"/> > <memnode cellid="2" mode="strict" nodeset="2"/> > <memnode cellid="3" mode="...

...cpu='27' cpuset='27' /><vcpupin vcpu='28' cpuset='28' /><vcpupin vcpu='29' cpuset='29' /><vcpupin vcpu='30' cpuset='30' /><vcpupin vcpu='31' cpuset='31' /></cputune> <numatune> <memnode cellid="0" mode="strict" nodeset="0"/> <memnode cellid="1" mode="strict" nodeset="1"/> <memnode cellid="2" mode="strict" nodeset="2"/> <memnode cellid="3" mode="strict" no...

Author: mishra Repository: /hg/zfs-crypto/gate Revision: 4fe0619163c071a1d2de7f6d6c99569485758c3c Log message: 6312695 memnode.h deliverable is present on sun4u/sun4v but not on x86 platform. Files: update: usr/src/pkgdefs/SUNWhea/prototype_i386

...c/uts/common/vm/page.h update: usr/src/uts/common/vm/seg_vn.c update: usr/src/uts/common/vm/vm_anon.c update: usr/src/uts/common/vm/vm_page.c update: usr/src/uts/common/vm/vm_pagelist.c update: usr/src/uts/i86pc/ml/locore.s update: usr/src/uts/i86pc/os/lgrpplat.c update: usr/src/uts/i86pc/os/memnode.c update: usr/src/uts/i86pc/os/mlsetup.c update: usr/src/uts/i86pc/os/mp_startup.c update: usr/src/uts/i86pc/sys/memnode.h update: usr/src/uts/i86pc/vm/vm_dep.h update: usr/src/uts/i86pc/vm/vm_machdep.c update: usr/src/uts/sun4/os/lgrpplat.c update: usr/src/uts/sun4/os/memnode.c update: usr...

...t merges loads in MergeConsecutiveStores. Two 16bit loads have been merged to one 32bit load, and two 16bit stores have been combined to one 32bit store. And then the code goes like this: // Replace one of the loads with the new load. LoadSDNode *Ld = cast<LoadSDNode>(LoadNodes[0].MemNode); DAG.ReplaceAllUsesOfValueWith(SDValue(Ld, 1), SDValue(NewLoad.getNode(), 1)); // Remove the rest of the load chains. for (unsigned i = 1; i < NumElem ; ++i) { // Replace all chain users of the old load nodes with the chain of the new // loa...

...rlap ... OK 328) QEMU XML-2-ARGV cputune-numatune ... OK 329) QEMU XML-2-ARGV numatune-memory ... OK 330) QEMU XML-2-ARGV numatune-memory-invalid-nodeset ... OK 331) QEMU XML-2-ARGV numatune-memnode ... libvirt: error : unsupported configuration: NUMA node 1 is unavailable FAILED 332) QEMU XML-2-ARGV numatune-memnode ... Got expected error: unsupported configuration: Per-node memory binding is not supported with this QEMU OK 333) QEMU XML-2-ARGV numatune-memnode-no-memory ... libvirt: error...

...fers to guest NUMA nodes. > > In "//numatune/memory[@nodeset]" I am telling libvirt to pin the > memory allocation to the guest from a particular host numa node. The <memory/> element tells what to do with not explicitly pinned guest NUMA nodes. > In "//numatune/memnode[@nodeset]" I am telling libvirt which guest > NUMA node (cellid) should come from which host NUMA node (nodeset). Correct. This way you can explicitly pin guest onto host NUMA nodes. > > In "//cpu/numa/cell[@id]" I am telling libvirt how much memory to > allocate to ea...

*facepalm* Now that I'm re-reading the documentation it's obvious that <page/> and @nodeset are for the guest, "This tells the hypervisor that the guest should have its memory allocated using hugepages instead of the normal native page size." Pretty clear there. Thank you SO much for the guidance, I'll return to my tweaking. I'll report back here with my results.

...t; >> In "//numatune/memory[@nodeset]" I am telling libvirt to pin the >> memory allocation to the guest from a particular host numa node. > > The <memory/> element tells what to do with not explicitly pinned guest > NUMA nodes. > >> In "//numatune/memnode[@nodeset]" I am telling libvirt which guest >> NUMA node (cellid) should come from which host NUMA node (nodeset). > > Correct. This way you can explicitly pin guest onto host NUMA nodes. > >> >> In "//cpu/numa/cell[@id]" I am telling libvirt how much memor...

...ges/page[@nodeset]" I am telling libvirt to use hugepages for the guest, and to get those hugepages from a particular host NUMA node. In "//numatune/memory[@nodeset]" I am telling libvirt to pin the memory allocation to the guest from a particular host numa node. In "//numatune/memnode[@nodeset]" I am telling libvirt which guest NUMA node (cellid) should come from which host NUMA node (nodeset). In "//cpu/numa/cell[@id]" I am telling libvirt how much memory to allocate to each guest NUMA node (cell). Basically, I thought "nodeset", regardless of where i...

Hello, I have cluster with AMD EPYC 7351 cpu. Two CPUs per node. I have performance 8-NUMA configuration: This is from hypervizor: [root@hde10 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 64 On-line CPU(s) list: 0-63 Thread(s) per core: 2 Core(s) per socket: 16 Socket(s): 2 NUMA