From: Davidlohr Bueso <dave@stgolabs.net>
To: Hillf Danton <hdanton@sina.com>
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: Thu, 5 Sep 2024 16:29:41 -0700 [thread overview]
Message-ID: <jw5skccxwi3u7i2ieb2l5gamekobbiankxbdzcxtctd636fh4v@wrfgdmkomiu3> (raw)
In-Reply-To: <20240905215945.1909-1-hdanton@sina.com>
On Fri, 06 Sep 2024, Hillf Danton wrote:\n
>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.
Are you against proactive reclaim altogether (ie: memcg) or this patch in
particular, which extends its availability?
The benefits of proactive reclaim are well documented, and the community has
been overall favorable towards it. This operation is not meant to be generally
used, but there are real latency benefits to be had which are completely
unrelated to watermarks. Similarly, we have 'compact' as an alternative to
kcompactd (which was once upon a time part of kswapd).
next prev parent reply other threads:[~2024-09-05 23:29 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
2024-09-05 23:29 ` Davidlohr Bueso [this message]
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=jw5skccxwi3u7i2ieb2l5gamekobbiankxbdzcxtctd636fh4v@wrfgdmkomiu3 \
--to=dave@stgolabs.net \
--cc=akpm@linux-foundation.org \
--cc=hdanton@sina.com \
--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