[pve-devel] [PATCH] add numa options

Alexandre DERUMIER aderumier at odiso.com
Tue Dec 2 20:25:51 CET 2014


>>shared? That looks strange to me. 
I mean split across the both nodes.


I have check a little libvirt,
and I'm not sure, but I think that  memory-backend-ram is optionnal, to have autonuma.

It's more about cpu pinning/memory pinning on selected host node

Here an example for libvirt:
http://www.redhat.com/archives/libvir-list/2014-July/msg00715.html
"qemu: pass numa node binding preferences to qemu"

+-object memory-backend-ram,size=20M,id=ram-node0,host-nodes=3,policy=preferred \
+-numa node,nodeid=0,cpus=0,memdev=ram-node0 \
+-object memory-backend-ram,size=645M,id=ram-node1,host-nodes=0-7,policy=bind \
+-numa node,nodeid=1,cpus=1-27,cpus=29,memdev=ram-node1 \
+-object memory-backend-ram,size=23440M,id=ram-node2,\
+host-nodes=1-2,host-nodes=5,host-nodes=7,policy=bind \
+-numa node,nodeid=2,cpus=28,cpus=30-31,memdev=ram-node2 \

----- Mail original ----- 

De: "Dietmar Maurer" <dietmar at proxmox.com> 
À: "Alexandre DERUMIER" <aderumier at odiso.com> 
Cc: pve-devel at pve.proxmox.com 
Envoyé: Mardi 2 Décembre 2014 19:42:45 
Objet: RE: [pve-devel] [PATCH] add numa options 

> "When do memory hotplug, if there is numa node, we should add the memory 
> size to the corresponding node memory size. 
> 
> For now, it mainly affects the result of hmp command "info numa"." 
> 
> 
> So, it's seem to be done automaticaly. 
> Not sure on which node is assigne the pc-dimm, but maybe the free slots are 
> shared at start between the numa nodes. 

shared? That looks strange to me. 



More information about the pve-devel mailing list