]>
Commit | Line | Data |
---|---|---|
e4a5c33e | 1 | =============================== |
1da177e4 | 2 | Numa policy hit/miss statistics |
e4a5c33e | 3 | =============================== |
1da177e4 LT |
4 | |
5 | /sys/devices/system/node/node*/numastat | |
6 | ||
7 | All units are pages. Hugepages have separate counters. | |
8 | ||
e4a5c33e | 9 | =============== ============================================================ |
36519c9e GL |
10 | numa_hit A process wanted to allocate memory from this node, |
11 | and succeeded. | |
12 | ||
13 | numa_miss A process wanted to allocate memory from another node, | |
14 | but ended up with memory from this node. | |
15 | ||
16 | numa_foreign A process wanted to allocate on this node, | |
17 | but ended up with memory from another one. | |
18 | ||
19 | local_node A process ran on this node and got memory from it. | |
20 | ||
21 | other_node A process ran on this node and got memory from another node. | |
22 | ||
23 | interleave_hit Interleaving wanted to allocate from this node | |
24 | and succeeded. | |
e4a5c33e | 25 | =============== ============================================================ |
1da177e4 LT |
26 | |
27 | For easier reading you can use the numastat utility from the numactl package | |
36519c9e | 28 | (http://oss.sgi.com/projects/libnuma/). Note that it only works |
1da177e4 LT |
29 | well right now on machines with a small number of CPUs. |
30 |