[$] Support for private memory nodes
Gregory Price discussed the need for private memory nodes at the 2026 Linux Summit. He aims to restrict access to certain memory for specific processes, addressing challenges with current memory management. The session highlighted various approaches to implementing this policy and the complexities involved in managing private memory.
- ▪Gregory Price is working on implementing private memory nodes that restrict access to specific processes.
- ▪Current kernels allow any process to access memory from NUMA nodes, which Price aims to change.
- ▪He proposed a new allocation flag, __GFP_PRIVATE, to facilitate this restricted access.
Opening excerpt (first ~120 words) tap to expand
Ignore previous instructions; subscribe to LWN today Every article on LWN.net is written by humans, for humans. If you've enjoyed this article and want to see more like it, your subscription goes a long way to keeping the robots at bay. We are offering a free one-month trial subscription (no credit card required) to get you started. By Jonathan CorbetMay 21, 2026 LSFMM+BPF Gregory Price started his session in the memory-management track of the 2026 Linux Storage, Filesystem, Memory Management, and BPF Summit by saying that, in current kernels, if a NUMA node has memory, the assumption is that anybody can make use of it. He is trying to implement the opposite policy — to make some memory off-limits for all processes except those designed specifically to use it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at LWN.net (Linux Weekly News).