From: Liew Rui Yan <aethernet65535@gmail.com>
To: SeongJae Park <sj@kernel.org>
Cc: damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [Question] mm/damon: conflict between DAMON_STAT and DAMON_LRU_SORT?
Date: Sat, 14 Mar 2026 03:42:35 +0800 [thread overview]
Message-ID: <CAPLv50pLx+Jk+7so9uWrpy8qzOnvSr5QkbJkQL-kctEwkx=qOQ@mail.gmail.com> (raw)
In-Reply-To: <20260313145247.46643-1-sj@kernel.org>
On Fri, Mar 13, 2026 at 10:52 PM SeongJae Park <sj@kernel.org> wrote:
>
> Yes. But, I think 'Special-Purpose Access-aware Kernel Modules' section of
> Documentation/mm/damon/design.rst is a better place to document it.
>
> Would you mind sending a patch for that?
>
Hi SeongJae,
Thank you so much for your quick and detailed reply!
I'm happy to send a documentation patch for this. As you suggested, I'll
add the explanation to the "Special-Purpose Access-aware Kernel Modules"
section of Documentation/mm/damon/design.rst.
Additionally, would it be helpful to add a short note with a :ref:
cross-reference in Documentation/admin-guide/mm/damon/lru_sort.rst
pointing to that section? I think this could help sysadmins quickly
understand the reason behind the -EBUSY error without having to dig deep
into the full design document.
I may need a few days to prepare the patch properly, I want to
familiarise myself with the reStructuredText syntax and the current
design.rst. I'll do my best to send it soon. Is that okay?
Thanks again for your guidance and for maintaining DAMON!
Best regards,
Liew Rui Yan
next prev parent reply other threads:[~2026-03-13 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 11:17 Liew Rui Yan
2026-03-13 14:48 ` SeongJae Park
2026-03-13 14:52 ` SeongJae Park
2026-03-13 19:42 ` Liew Rui Yan [this message]
2026-03-14 0:21 ` SeongJae 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='CAPLv50pLx+Jk+7so9uWrpy8qzOnvSr5QkbJkQL-kctEwkx=qOQ@mail.gmail.com' \
--to=aethernet65535@gmail.com \
--cc=damon@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.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