[SERVER-9181] Instead of grubbing around in /proc/self, use libnuma to query (and potentially alter) numa configuration at startup Created: 29/Mar/13 Updated: 26/Oct/21 Resolved: 26/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | features we're not sure of |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Currently, we detect if we are on a numa machine by examining /sys/devices, and detect how numa is configured by looking at /proc/self/numa_maps. We then issue a warning. A better way to do this, on machines new enough to offer it, is to use libnuma to query the numa state. Potentially, we could also change the interleave state as well with numa_set_interleave_mask. This would both protect us from future changes to /proc and /sys, and give us finer grained control over our NUMA story. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 30/Mar/13 ] |
|
should at least think about a hybrid |