[PATCH v2 51/61] mm/memcontrol: Stop using mm->highest_vm_end

Liam Howlett liam.howlett at oracle.com
Tue Aug 17 08:47:31 PDT 2021


From: "Liam R. Howlett" <Liam.Howlett at Oracle.com>

Signed-off-by: Liam R. Howlett <Liam.Howlett at Oracle.com>
---
 mm/memcontrol.c | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 3e7c205a1852..943e8554a4bb 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -5830,7 +5830,7 @@ static unsigned long mem_cgroup_count_precharge(struct mm_struct *mm)
 	unsigned long precharge;
 
 	mmap_read_lock(mm);
-	walk_page_range(mm, 0, mm->highest_vm_end, &precharge_walk_ops, NULL);
+	walk_page_range(mm, 0, -1, &precharge_walk_ops, NULL);
 	mmap_read_unlock(mm);
 
 	precharge = mc.precharge;
@@ -6128,9 +6128,7 @@ static void mem_cgroup_move_charge(void)
 	 * When we have consumed all precharges and failed in doing
 	 * additional charge, the page walk just aborts.
 	 */
-	walk_page_range(mc.mm, 0, mc.mm->highest_vm_end, &charge_walk_ops,
-			NULL);
-
+	walk_page_range(mc.mm, 0, -1, &charge_walk_ops, NULL);
 	mmap_read_unlock(mc.mm);
 	atomic_dec(&mc.from->moving_account);
 }
-- 
2.30.2



More information about the maple-tree mailing list