Message ID | 20250419053824.1601470-1-gourry@gourry.net (mailing list archive) |
---|---|
Headers | show |
Series | vmscan: enforce mems_effective during demotion | expand |
On Sat, Apr 19, 2025 at 01:38:22AM -0400, Gregory Price wrote: > Change reclaim to respect cpuset.mems_effective during demotion when > possible. Presently, reclaim explicitly ignores cpuset.mems_effective > when demoting, which may cause the cpuset settings to violated. > > Implement cpuset_node_allowed() to check the cpuset.mems_effective > associated wih the mem_cgroup of the lruvec being scanned. > > This requires renaming the existing cpuset_node_allowed() to be > cpuset_current_now_allowed() - which is more descriptive anyway - to > implement the new cpuset_node_allowed() which takes a target cgroup. > > v3: > - remove cgroup indirection, call cpuset directly from memcontrol > - put mem_cgroup_node_allowed in memcontrol.c to reduce cpuset.h > include scope > - return true if mems_effective is empty, and don't walk the parents > as recommended by Waiman Long. > > Gregory Price (2): > cpuset: rename cpuset_node_allowed to cpuset_current_node_allowed > vmscan,cgroup: apply mems_effective to reclaim From cgroup POV: Acked-by: Tejun Heo <tj@kernel.org> Given that the operative changes are mostly in mm, it'd probably be best to route through -mm, but please let me know if you wanna go through the cgroup tree. Thanks.