From: Liew Rui Yan <aethernet65535@gmail.com>
To: sj@kernel.org
Cc: aethernet65535@gmail.com, damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH 1/3] docs/mm/damon/design: accurate semantics of nr_snapshots
Date: Wed, 12 Aug 2026 01:01:39 +0800 [thread overview]
Message-ID: <20260811170139.32342-1-aethernet65535@gmail.com> (raw)
In-Reply-To: <20260811134634.4407-1-sj@kernel.org>
On Tue, 11 Aug 2026 06:46:33 -0700 SJ Park <sj@kernel.org> wrote:
> On Tue, 11 Aug 2026 18:18:39 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
>
> > Change "tried to be applied" -> "tried to be completely applied" to
> > maintain consistency between the documentation and the code.
>
> It feels bit confusing to me. The completion in this context is for "trial",
> not "application". For example, someone might wrongly think the number could
> be incremented even if a scheme was "tried" to be completely "applied" to the
> snapshot, but failed due to a quota.
>
> What about "completely tried to be applied"?
Thank you for your clarification.
"Tried to be __completely applied__" means that even if only a portion
is tried, it will still increase. "__Completely tried__ to be applied"
means that it will only increase if it is fully tried. Right?
I will change this in next revision.
Best regards,
Rui Yan
next prev parent reply other threads:[~2026-08-11 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 10:18 [PATCH 0/3] docs/mm/damon/design: add explanation of nr_snapshots Liew Rui Yan
2026-08-11 10:18 ` [PATCH 1/3] docs/mm/damon/design: accurate semantics " Liew Rui Yan
2026-08-11 13:46 ` SJ Park
2026-08-11 17:01 ` Liew Rui Yan [this message]
2026-08-11 10:18 ` [PATCH 2/3] docs/mm/damon/design: difference between watermarks and nr_snapshots Liew Rui Yan
2026-08-11 13:48 ` SJ Park
2026-08-11 10:18 ` [PATCH 3/3] docs/mm/damon/design: fix typo of max_nr_snapshots Liew Rui Yan
2026-08-11 13:52 ` SJ Park
2026-08-11 13:56 ` [PATCH 0/3] docs/mm/damon/design: add explanation of nr_snapshots SJ Park
2026-08-11 17:02 ` Liew Rui Yan
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=20260811170139.32342-1-aethernet65535@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