From: Davidlohr Bueso <dave@stgolabs.net>
To: Roman Gushchin <roman.gushchin@linux.dev>
Cc: akpm@linux-foundation.org, mhocko@kernel.org, hannes@cmpxchg.org,
shakeel.butt@linux.dev, yosryahmed@google.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] mm/memcg: make memory.reclaim interface generic
Date: Thu, 17 Jul 2025 09:35:36 -0700 [thread overview]
Message-ID: <20250717163536.6jwhdzpb5a4elm4z@offworld> (raw)
In-Reply-To: <87bjpjshn7.fsf@linux.dev>
On Wed, 16 Jul 2025, Roman Gushchin wrote:
>Davidlohr Bueso <dave@stgolabs.net> writes:
>
>> This adds a general call for both parsing as well as the
>> common reclaim semantics. memcg is still the only user and
>> no change in semantics.
>>
>> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
>> ---
>> mm/internal.h | 2 +
>> mm/memcontrol.c | 77 ++------------------------------------
>> mm/vmscan.c | 98 +++++++++++++++++++++++++++++++++++++++++++++++++
>> 3 files changed, 104 insertions(+), 73 deletions(-)
>> ...
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index c13c01eb0b42..63ddec550c3b 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -57,6 +57,7 @@
>> #include <linux/rculist_nulls.h>
>> #include <linux/random.h>
>> #include <linux/mmu_notifier.h>
>> +#include <linux/parser.h>
>>
>> #include <asm/tlbflush.h>
>> #include <asm/div64.h>
>> @@ -6714,6 +6715,15 @@ unsigned long try_to_free_mem_cgroup_pages(struct mem_cgroup *memcg,
>>
>> return nr_reclaimed;
>> }
>> +#else
>> +unsigned long try_to_free_mem_cgroup_pages(struct mem_cgroup *memcg,
>> + unsigned long nr_pages,
>> + gfp_t gfp_mask,
>> + unsigned int reclaim_options,
>> + int *swappiness)
>> +{
>> + return 0;
>> +}
>> #endif
>>
>> static void kswapd_age_node(struct pglist_data *pgdat, struct scan_control *sc)
>> @@ -7708,6 +7718,94 @@ int node_reclaim(struct pglist_data *pgdat, gfp_t gfp_mask, unsigned int order)
>>
>> return ret;
>> }
>> +
>> +enum {
>> + MEMORY_RECLAIM_SWAPPINESS = 0,
>> + MEMORY_RECLAIM_SWAPPINESS_MAX,
>> + MEMORY_RECLAIM_NULL,
>> +};
>> +static const match_table_t tokens = {
>> + { MEMORY_RECLAIM_SWAPPINESS, "swappiness=%d"},
>> + { MEMORY_RECLAIM_SWAPPINESS_MAX, "swappiness=max"},
>> + { MEMORY_RECLAIM_NULL, NULL },
>> +};
>> +
>> +int user_proactive_reclaim(char *buf, struct mem_cgroup *memcg, pg_data_t *pgdat)
>> +{
>> + unsigned int nr_retries = MAX_RECLAIM_RETRIES;
>> + unsigned long nr_to_reclaim, nr_reclaimed = 0;
>> + int swappiness = -1;
>> + char *old_buf, *start;
>> + substring_t args[MAX_OPT_ARGS];
>> +
>> + if (!buf || (!memcg && !pgdat))
>> + return -EINVAL;
>> +
>> + buf = strstrip(buf);
>> +
>> + old_buf = buf;
>> + nr_to_reclaim = memparse(buf, &buf) / PAGE_SIZE;
>> + if (buf == old_buf)
>> + return -EINVAL;
>> +
>> + buf = strstrip(buf);
>
>To be honest, not a big fan of this refactoring. Effectively parts of
>the memcg user interface are moved into mm/vmscan.c. I get that you want
>to use the exact same interface somewhere else, but still...
I disagree, further this is no different than other callers in vmscan.c
around memcg.
>Is it possible to keep it in mm/memcontrol.c?
Why? now proactive reclaim is not special to memcg... unless strong reasons
it makes little sense to keep it there.
>Also maybe split the actual reclaim mechanism and user's input parsing?
I tried something like this initially, and ended up prefering this way.
Further, this approach limits the reachability of the input parsing logic, and
the interface is already being an exception to the one-value per file "rule".
Thanks,
Davidlohr
next prev parent reply other threads:[~2025-07-17 16:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 18:58 [PATCH -next v2 0/4] mm: per-node proactive reclaim Davidlohr Bueso
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 [this message]
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=20250717163536.6jwhdzpb5a4elm4z@offworld \
--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).