hugetlb: numa control of persistent huge pages alloc/free
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 25 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | hugetlb: rework hstate_next_node_* functionsmm/ | +45 | 1 reply | |
| 2/5 | hugetlb: add nodemask arg to huge page alloc, free and surplus adjust fcnsmm/ | +67 | 4 replies | |
| 3/5 | hugetlb: derive huge pages nodes allowed from task mempolicyinclude/ mm/ mm/ | +73 | 4 replies | |
| 4/5 | hugetlb: add per node hstate attributesdrivers/ include/ include/ +1 more | +197 | 16 replies | |
| 5/5 | hugetlb: update hugetlb documentation for mempolicy based management.Documentation/ | +172 | 0 replies |
Reviews trailers per patch
3 of 5 patches have a Reviewed-by or Acked-by.
| Patch | Mel Gorman | David Rientjes |
|---|---|---|
| 1/5 | R-b | A-b |
| 2/5 | R-b | |
| 3/5 | A-b | |
| 4/5 | ||
| 5/5 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/5] hugetlb: numa control of persistent huge pages alloc/free
PATCH 0/5 hugetlb: numa control of persistent huge pages alloc/free
Against: 2.6.31-rc6-mmotm-090820-1918
This is V4 of a series of patches to provide control over the location of the allocation and freeing of persistent huge pages on a NUMA
platform. This series uses the task NUMA mempolicy of the task
modifying "nr_hugepages" to constrain the affected nodes. This method is based on Mel Gorman's suggestion to use task mempolicy. One of the benefits of this method is that it does not *require* modification to hugeadm(8) to use this feature. One of the possible downsides is that task mempolicy is limited by cpuset constraints.
V4 add a subset of the hugepages sysfs attributes to each per node system device directory under:
/sys/devices/node/node[0-9]*/hugepages.
The per node attibutes allow direct assignment of a huge page count on a specific node, regardless of the task's mempolicy or cpuset constraints.
Note, I haven't implemented a boot time parameter to constrain the boot time allocation of huge pages. This can be added if anyone feels strongly that it is required.