From: Jinjie Ruan <ruanjinjie@huawei.com>
To: SJ Park <sj@kernel.org>
Cc: <corbet@lwn.net>, <skhan@linuxfoundation.org>,
<rdunlap@infradead.org>, <damon@lists.linux.dev>,
<linux-mm@kvack.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Docs/admin-guide/mm/damon/reclaim: document how to disable watermarks
Date: Wed, 28 Oct 2026 14:09:39 +0800 [thread overview]
Message-ID: <b0fb80cc-4a0d-4612-beef-bf2fc398f06e@huawei.com> (raw)
In-Reply-To: <20261028053525.155909-1-sj@kernel.org>
在 2026/10/28 13:35, SJ Park 写道:
> On Tue, 27 Oct 2026 22:24:24 -0700 SJ Park <sj@kernel.org> wrote:
>
>> Hello Jinjie,
>>
>> On Wed, 28 Oct 2026 10:36:28 +0800 Jinjie Ruan <ruanjinjie@huawei.com> wrote:
>>
>>> DAMON_RECLAIM runs its scheme only while the free memory rate is
>>> between `wmarks_low` and `wmarks_mid`.
>>>
>>> But some users want to reclaim cold pages even while the system has
>>> plenty of free memory, and it is not obvious that the existing
>>> watermarks parameters can already do that. So Document the setup.
>>
>> Thank you for this patch!
>>
>>>
>>> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
>>> ---
>>> Documentation/admin-guide/mm/damon/reclaim.rst | 7 +++++++
>>> 1 file changed, 7 insertions(+)
>>>
>>> diff --git a/Documentation/admin-guide/mm/damon/reclaim.rst b/Documentation/admin-guide/mm/damon/reclaim.rst
>>> index ec7e3e32b4ac..23fede7d1cdb 100644
>>> --- a/Documentation/admin-guide/mm/damon/reclaim.rst
>>> +++ b/Documentation/admin-guide/mm/damon/reclaim.rst
>>> @@ -193,6 +193,13 @@ DAMON_RECLAIM becomes inactive, so it does nothing but periodically checks the
>>> watermarks. In the case, the system falls back to the LRU-list based page
>>> granularity reclamation logic.
>>>
>>> +To keep DAMON_RECLAIM always active regardless of the free memory rate, set
>>> +``wmarks_high``, ``wmarks_mid`` and ``wmarks_low`` to ``1000``, ``1000`` and
>>> +``0``, respectively. Then the reclamation is limited only by ``min_age`` and
>>> +the quotas. This is useful for reclaiming cold pages even while the system
>>> +has plenty of free memory, e.g., right after an idle virtual machine is
>>> +paused.
>>> +
>>
>> I feel like above might be too detailed. Particularly, the second sentence
>> looks too detailed. In a sense, it is not technically correct because of
>> 'skip_anon' parameter. We might later need to add more such controls, and I
>> concern if this kind of detailed documentation will limit such extensions.
>>
>> What about keeping only the first sentence and dropping later two sentences?
>
> If you don't mind, I could add this patch to damon/next after dropping the last
> two sentences on my own.
Hi SJ,
It is fine with me, thanks. Please go ahead.
>
>
> Thanks,
> SJ
>
> [...]
--
Best regards,
Jinjie
next prev parent reply other threads:[~2026-10-28 6:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 2:36 [PATCH] Docs/admin-guide/mm/damon/reclaim: document how to disable watermarks Jinjie Ruan
2026-10-28 5:24 ` SJ Park
2026-10-28 5:35 ` SJ Park
2026-10-28 6:09 ` Jinjie Ruan [this message]
2026-10-28 14:08 ` SJ Park
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=b0fb80cc-4a0d-4612-beef-bf2fc398f06e@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=sj@kernel.org \
--cc=skhan@linuxfoundation.org \
/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