From: Hillf Danton <hdanton@sina.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: yosryahmed@google.com, mhocko@kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] mm: introduce per-node proactive reclaim interface
Date: Fri, 6 Sep 2024 05:59:45 +0800 [thread overview]
Message-ID: <20240905215945.1909-1-hdanton@sina.com> (raw)
In-Reply-To: <20240904162740.1043168-1-dave@stgolabs.net>
On Wed, 4 Sep 2024 09:27:40 -0700 Davidlohr Bueso <dave@stgolabs.net> wrote:
> 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
>
The proactive reclaim on the cmdline looks like waste of cpu cycles before
the cases where kswapd fails to work are spotted. It is not correct to add
it because you can type the code.
next prev parent reply other threads:[~2024-09-05 22:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 16:27 Davidlohr Bueso
2024-09-04 20:18 ` Andrew Morton
2024-09-05 1:08 ` Davidlohr Bueso
2024-09-05 1:15 ` Andrew Morton
2024-09-05 3:35 ` Davidlohr Bueso
2024-09-05 7:31 ` Yosry Ahmed
2024-09-04 21:29 ` Yosry Ahmed
2024-09-05 21:59 ` Hillf Danton [this message]
2024-09-05 23:29 ` Davidlohr Bueso
2024-09-06 11:04 ` Hillf Danton
2024-09-09 7:12 ` Michal Hocko
2024-09-09 10:51 ` Hillf Danton
2024-09-09 14:50 ` Michal Hocko
2024-09-09 7:20 ` Michal Hocko
2024-09-10 16:31 ` Davidlohr Bueso
2024-09-11 6:49 ` Michal Hocko
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=20240905215945.1909-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--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