Manual Pages  — NUMA

In a NUMA architecture, the latency to access specific memory or IO devices depends upon which processor the memory or device is attached to. Accessing memory local to a processor is faster than accessing memory that is connected to one of the other processors. FreeBSD implements NUMA-aware memory allocation policies. By default it attempts to ensure that allocations are balanced across each domain. Users may override the default domain selection policy using cpuset(1).

NUMA support is enabled when the NUMA option is specified in the kernel configuration file. Each platform defines the MAXMEMDOM constant, which specifies the maximum number of supported NUMA domains. This constant may be specified in the kernel configuration file. NUMA support can be disabled at boot time by setting the vm.numa.disabled tunable to 1. Other values for this tunable are currently ignored.

Thread and process NUMA policies are controlled with the cpuset_getdomain(2) and cpuset_setdomain(2) syscalls. The cpuset(1) tool is available for starting processes with a non-default policy, or to change the policy of an existing thread or process.

Systems with non-uniform access to I/O devices may mark those devices with the local VM domain identifier. Drivers can find out their local domain information by calling bus_get_domain(9).

vm.ndomains
	The number of VM domains which have been detected.
vm.phys_locality
	A table indicating the relative cost of each VM domain to each other. A value of 10 indicates equal cost. A value of -1 means the locality map is not available or no locality information is available.
vm.phys_segs
	The map of physical memory, grouped by VM domain.