numa - overview of Non-Uniform Memory Architecture
Non-Uniform Memory Access (NUMA) refers to multiprocessor systems whose memory is divided into multiple memory nodes. The access time of a memory node depends on the relative locations of the accessing CPU and the accessed node. (This contrasts with a symmetric multiprocessor system, where the access time for all of the memory is the same for all CPUs.) Normally, each CPU on a NUMA system has a local memory node whose contents can be accessed faster than the memory in the node local to another CPU or the memory on a bus shared by all CPUs. NUMA system calls The Linux kernel implements the following NUMA-related system calls: get_mempolicy(2), mbind(2), migrate_pages(2), move_pages(2), and set_mempolicy(2). However, applications should normally use the interface provided by libnuma; see "Library Support" below. /proc/[number]/numa_maps (since Linux 2.6.14) This file displays information about a process's NUMA memory policy and allocation. Each line contains information about a memory range used by the process, displaying---among other information---the effective memory policy for that memory range and on which nodes the pages have been allocated. numa_maps is a read-only file. When /proc/<pid>/numa_maps is read, the kernel will scan the virtual address space of the process and report how memory is used. One line is displayed for each unique memory range of the process. The first field of each line shows the starting address of the memory range. This field allows a correlation with the contents of the /proc/<pid>/maps file, which contains the end address of the range and other information, such as the access permissions and sharing. The second field shows the memory policy currently in effect for the memory range. Note that the effective policy is not necessarily the policy installed by the process for that memory range. Specifically, if the process installed a "default" policy for that range, the effective policy for that range will be the process policy, which may or may not be "default". The rest of the line contains information about the pages allocated in the memory range, as follows: N<node>=<nr_pages> The number of pages allocated on <node>. <nr_pages> includes only pages currently mapped by the process. Page migration and memory reclaim may have temporarily unmapped pages associated with this memory range. These pages may show up again only after the process has attempted to reference them. If the memory range represents a shared memory area or file mapping, other processes may currently have additional pages mapped in a corresponding memory range. file=<filename> The file backing the memory range. If the file is mapped as private, write accesses may have generated COW (Copy-On-Write) pages in this memory range. These pages are displayed as anonymous pages. heap Memory range is used for the heap. stack Memory range is used for the stack. huge Huge memory range. The page counts shown are huge pages and not regular sized pages. anon=<pages> The number of anonymous page in the range. dirty=<pages> Number of dirty pages. mapped=<pages> Total number of mapped pages, if different from dirty and anon pages. mapmax=<count> Maximum mapcount (number of processes mapping a single page) encountered during the scan. This may be used as an indicator of the degree of sharing occurring in a given memory range. swapcache=<count> Number of pages that have an associated entry on a swap device. active=<pages> The number of pages on the active list. This field is shown only if different from the number of pages in this range. This means that some inactive pages exist in the memory range that may be removed from memory by the swapper soon. writeback=<pages> Number of pages that are currently being written out to disk.
No standards govern NUMA interfaces.
The Linux NUMA system calls and /proc interface are available only if the kernel was configured and built with the CONFIG_NUMA option. Library support Link with -lnuma to get the system call definitions. libnuma and the required <numaif.h> header are available in the numactl package. However, applications should not use these system calls directly. Instead, the higher level interface provided by the numa(3) functions in the numactl package is recommended. The numactl package is available at ftp://oss.sgi.com/www/projects/libnuma/download/. The package is also included in some Linux distributions. Some distributions include the development library and header in the separate numactl-devel package.
get_mempolicy(2), mbind(2), move_pages(2), set_mempolicy(2), numa(3), cpuset(7), numactl(8)
This page is part of release 4.09 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
More Linux Commands
glutPopWindow(3) - change the stacking order of the current
glutPopWindow and glutPushWindow work on both top-level windows and subwindows. The effect of pushing and popping windows does not take place immediately. Inste
__free_hook(3) malloc debugging variables - Linux man page
The GNU C library lets you modify the behavior of malloc(3), realloc(3), and free(3) by specifying appropriate hook functions. You can use these hooks to help y
PerlIO(3pm) - On demand loader for PerlIO layers and root of
When an undefined layer foo is encountered in an open or binmode layer specification then C code performs the equivalent of: use PerlIO foo; The perl code in Pe
XkbQueryExtension(3) - Determines the compatibility of a lib
Call XkbQueryExtension to check for the presence and compatibility of the extension in the server and to initialize the extension. Because of potential version
innxmit(8) - Send Usenet articles to a remote NNTP server...
innxmit connects to the NNTP server at the specified host (validating itself via passwd.nntp if possible) and sends it the articles specified in the batch file
feupdateenv(3) - floating-point rounding and exception handl
These eleven functions were defined in C99, and describe the handling of floating-point rounding and exceptions (overflow, zero-divide, etc.). Exceptions The di
411toppm.1 - 411toppm(1) - convert Sony Mavica .411 image to PPM lbAC....
This program is part of Netpbm(1) 411toppm reads a .411 file, such as from a Sony Mavic camera, and converts it to a PPM image as output. Output is to Standard
glPopMatrix(3gl) - push and pop the current matrix stack....
There is a stack of matrices for each of the matrix modes. In GL_MODELVIEW mode, the stack depth is at least 32. In the other modes, GL_COLOR, const(PROJECTION)
isdn_audio.4 (Manual - Linux man page).....................
This document describes the audio related extensions of the modem emulation, provided by /dev/ttyIx. The ISDN tty devices are equipped with a modem emulation im
crypttab(5) - static information about crypted filesystems
The /etc/crypttab file describes encrypted block devices that are set up during system boot. Empty lines and lines starting with the # character are ignored. Ea
wmemchr(3) - search a wide character in a wide-character arr
The wmemchr() function is the wide-character equivalent of the memchr(3) function. It searches the n wide characters starting at s for the first occurrence of t
islower(3) - character classification routines (Man Page)...
These functions check whether c, which must have the value of an unsigned char or EOF, falls into a certain character class according to the specified locale. T