Assorted cleanups from numa-aware-vswitches series
Resolve open issues from preceding patches. Part of blueprint numa-aware-vswitches Change-Id: I0c35109b67aa94cf19a4d20a97bf5ab15cf3db4e
This commit is contained in:
committed by
Dan Smith
parent
803f85d7e6
commit
24c016ed6c
@@ -31,13 +31,13 @@ Simultaneous Multi-Threading (SMT)
|
||||
CPUs on the system and can execute workloads in parallel. However, as with
|
||||
NUMA, threads compete for shared resources.
|
||||
|
||||
Non Uniform I/O Access (NUMA I/O)
|
||||
Non-Uniform I/O Access (NUMA I/O)
|
||||
In a NUMA system, I/O to a device mapped to a local memory region is more
|
||||
efficient than I/O to a remote device. A device connected to the same socket
|
||||
providing the CPU and memory offers lower latencies for I/O operations due to
|
||||
its physical proximity. This generally manifests itself in devices connected
|
||||
to the PCIe bus, such as NICs or vGPUs, but applies to any device support
|
||||
memory mapped I/O.
|
||||
memory-mapped I/O.
|
||||
|
||||
In OpenStack, SMP CPUs are known as *cores*, NUMA cells or nodes are known as
|
||||
*sockets*, and SMT CPUs are known as *threads*. For example, a quad-socket,
|
||||
|
||||
Reference in New Issue
Block a user