[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aHiouwRh_Z7MPfV-@tiehlicka>
Date: Thu, 17 Jul 2025 09:39:39 +0200
From: Michal Hocko <mhocko@...e.com>
To: Hillf Danton <hdanton@...a.com>
Cc: Davidlohr Bueso <dave@...olabs.net>, akpm@...ux-foundation.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
On Thu 17-07-25 14:49:24, Hillf Danton wrote:
> 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?
Usecases are described in the section of the email you haven't quoted in your reply.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists