From: Davidlohr Bueso <dave@stgolabs.net>
To: akpm@linux-foundation.org
Cc: mhocko@kernel.org, hannes@cmpxchg.org, roman.gushchin@linux.dev,
shakeel.butt@linux.dev, yosryahmed@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
dave@stgolabs.net
Subject: [PATCH -next v2 0/4] mm: per-node proactive reclaim
Date: Mon, 23 Jun 2025 11:58:47 -0700 [thread overview]
Message-ID: <20250623185851.830632-1-dave@stgolabs.net> (raw)
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
next reply other threads:[~2025-06-23 18:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 18:58 Davidlohr Bueso [this message]
2025-06-23 18:58 ` [PATCH 1/4] mm/vmscan: respect psi_memstall region in node reclaim Davidlohr Bueso
2025-06-25 17:08 ` Shakeel Butt
2025-07-17 1:44 ` Roman Gushchin
2025-06-23 18:58 ` [PATCH 2/4] mm/memcg: make memory.reclaim interface generic Davidlohr Bueso
2025-06-23 21:45 ` Andrew Morton
2025-06-23 23:36 ` Davidlohr Bueso
2025-06-24 18:26 ` Klara Modin
2025-07-17 1:58 ` Roman Gushchin
2025-07-17 16:35 ` Davidlohr Bueso
2025-07-17 22:17 ` Shakeel Butt
2025-07-17 22:52 ` Andrew Morton
2025-07-17 23:56 ` Davidlohr Bueso
2025-07-18 0:17 ` Shakeel Butt
2025-06-23 18:58 ` [PATCH 3/4] mm/vmscan: make __node_reclaim() more generic Davidlohr Bueso
2025-07-17 2:03 ` Roman Gushchin
2025-07-17 22:25 ` Shakeel Butt
2025-06-23 18:58 ` [PATCH 4/4] mm: introduce per-node proactive reclaim interface Davidlohr Bueso
2025-06-25 23:10 ` Shakeel Butt
2025-06-27 19:07 ` SeongJae Park
2025-07-17 2:46 ` Roman Gushchin
2025-07-17 16:26 ` Davidlohr Bueso
2025-07-17 22:46 ` Andrew Morton
[not found] ` <20250717064925.2304-1-hdanton@sina.com>
2025-07-17 7:39 ` Michal Hocko
2025-07-17 22:28 ` Shakeel Butt
2025-06-23 21:50 ` [PATCH -next v2 0/4] mm: per-node proactive reclaim Andrew Morton
2025-07-16 0:24 ` Andrew Morton
2025-07-16 15:15 ` Shakeel Butt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250623185851.830632-1-dave@stgolabs.net \
--to=dave@stgolabs.net \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=yosryahmed@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).