RFC cpuset,mm: fix memory spread bug
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | cpusets: restructure the function cpuset_update_task_memory_state()kernel/ | +19 | 0 replies | |
| 2/3 | cpusets: update tasks' page/slab spread flags in timekernel/ | +55 | 0 replies | |
| 3/3 | cpuset,mm: update tasks' mems_allowed in timeinclude/ include/ init/ +4 more | +162 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/3] cpuset,mm: fix memory spread bug
The kernel still allocated the page caches on old node after modifying its cpuset's mems when 'memory_spread_page' was set, or it didn't spread the page cache evenly over all the nodes that faulting task is allowed to usr after memory_spread_page was set. it is caused by the old mem_allowed and flags of the task, the current kernel doesn't updates them unless some function invokes cpuset_update_task_memory_state(), it is too late sometimes.We must update the mem_allowed and the flags of the tasks in time.
Slab has the same problem.
The following patches fix this bug by updating tasks' mem_allowed and spread flag after its cpuset's mems or spread flag is changed.
patch 1: restructure the function cpuset_update_task_memory_state() patch 2: update tasks' page/slab spread flags in time patch 3: update tasks' mems_allowed in time
--
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>