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