[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250623185851.830632-1-dave@stgolabs.net>
Date: Mon, 23 Jun 2025 11:58:47 -0700
From: Davidlohr Bueso <dave@...olabs.net>
To: akpm@...ux-foundation.org
Cc: mhocko@...nel.org,
hannes@...xchg.org,
roman.gushchin@...ux.dev,
shakeel.butt@...ux.dev,
yosryahmed@...gle.com,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
dave@...olabs.net
Subject: [PATCH -next v2 0/4] mm: per-node proactive reclaim
Hello,
This is a tardy follow up to v1:
https://lore.kernel.org/linux-mm/20240904162740.1043168-1-dave@stgolabs.net/
Changes:
- Not a change perse, but further discussed with mhocko potential usecases
to justify upstreaming this interface. Nowadays NUMA represents the common
abstraction for memory tiering representing devices of various performance
characteristics. This interface makes a lot of sense given memcg's lack
of NUMA awareness.
- Consolidate both memcg and per-node flavors into a common helper. (Yosry)
Patch 1 is a small fixlet independent of the rest of the series.
Patches 2-3 make some of the machinery more generic.
Patch 4 adds the sysfs interface (which has further been deemed ok albeit
not following the one value per file "rule").
Please consider for v6.16.
Thanks!
Davidlohr Bueso (4):
mm/vmscan: respect psi_memstall region in node reclaim
mm/memcg: make memory.reclaim interface generic
mm/vmscan: make __node_reclaim() more generic
mm: introduce per-node proactive reclaim interface
Documentation/ABI/stable/sysfs-devices-node | 9 +
drivers/base/node.c | 2 +
include/linux/swap.h | 16 ++
mm/internal.h | 2 +
mm/memcontrol.c | 77 +-------
mm/vmscan.c | 195 +++++++++++++++++---
6 files changed, 201 insertions(+), 100 deletions(-)
--
2.39.5
Powered by blists - more mailing lists