November 29, 201411 yr I was trying to understand vcpupin and its application a little better. I started to read here since it was the first hit I got in google: http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/ch25s06.html I know it is Fedora but the concept of pinning the CPUs should be the same I assume. Anyway, the first part is what caught my interest: Identifying CPU and NUMA topology The first step in deciding what policy to apply is to determine the host’s memory and CPU topology. The virsh nodeinfo command provides information about how many sockets, cores and hyperthreads there are attached a host. Naturally, I decided to run this command on my system and it led to some confusion on my behalf: root@unRAID:~# virsh nodeinfo CPU model: x86_64 CPU(s): 16 CPU frequency: 1600 MHz CPU socket(s): 1 Core(s) per socket: 4 Thread(s) per core: 2 NUMA cell(s): 2 Memory size: 49523432 KiB Why did it report that I have only one CPU socket when I most definitely have two (as shown below)? root@unRAID:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 26 Stepping: 5 CPU MHz: 1600.000 BogoMIPS: 4800.11 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-3,8-11 NUMA node1 CPU(s): 4-7,12-15 John
Archived
This topic is now archived and is closed to further replies.