[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250717064925.2304-1-hdanton@sina.com>
Date: Thu, 17 Jul 2025 14:49:24 +0800
From: Hillf Danton <hdanton@...a.com>
To: Davidlohr Bueso <dave@...olabs.net>
Cc: akpm@...ux-foundation.org,
mhocko@...nel.org,
hannes@...xchg.org,
Roman Gushchin <roman.gushchin@...ux.dev>,
shakeel.butt@...ux.dev,
yosryahmed@...gle.com,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] mm: introduce per-node proactive reclaim interface
Davidlohr Bueso <dave@...olabs.net> writes:
> This adds support for allowing proactive reclaim in general on a
> NUMA system. A per-node interface extends support for beyond a
> memcg-specific interface, respecting the current semantics of
> memory.reclaim: respecting aging LRU and not supporting
> artificially triggering eviction on nodes belonging to non-bottom
> tiers.
>
> This patch allows userspace to do:
>
> echo "512M swappiness=10" > /sys/devices/system/node/nodeX/reclaim
>
When kswapd is active, this is not needed.
When kswapd is idle, why is this needed?
Powered by blists - more mailing lists