RFC Node-based reclaim/migration
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest1 patch 52 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | Expose per-node reclaim and migration to userspacedrivers/ fs/ include/ +4 more | +101 | 22 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/1] Node-based reclaim/migration
--
We're trying to use NUMA node isolation as a form of job resource control at Google, and the existing page migration APIs are all bound to individual processes and so are a bit clunky to use when you just want to affect all the pages on a given node.
How about an API to allow userspace to direct page migration (and page reclaim) on a per-node basis? This patch provides such an API, based around sysfs; a system call approach would certainly be possible too.
It sort of overlaps with memory hot-unplug, but is simpler since it's not so bad if we miss a few pages.
Comments? Also, can anyone clarify whether I need any locking when sacnning the pages in a pgdat? As far as I can see, even with memory hotplug this number can only increase, not decrease.
Paul
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>