From: SJ Park <sj@kernel.org>
To: Liew Rui Yan <aethernet65535@gmail.com>
Cc: SJ Park <sj@kernel.org>,
akpm@linux-foundation.org, corbet@lwn.net, damon@lists.linux.dev,
david@kernel.org, liam@infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org,
mhocko@suse.com, rdunlap@infradead.org, rppt@kernel.org,
skhan@linuxfoundation.org, surenb@google.com, vbabka@kernel.org
Subject: Re: [RFC PATCH] Docs/mm/damon/design: clarify when qt_exceeds increases
Date: Wed, 9 Sep 2026 17:17:46 -0700 [thread overview]
Message-ID: <20260910001747.110260-1-sj@kernel.org> (raw)
In-Reply-To: <20260909100913.30568-1-aethernet65535@gmail.com>
On Wed, 9 Sep 2026 18:07:33 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
> On Tue, 08 Sep 2026 17:38:00 -0700 SJ Park <sj@kernel.org> wrote:
>
> > Hi Liew,
> >
> > On Wed, 9 Sep 2026 01:50:23 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:
[...]
> > > By the way, I found a thing in the design document that confused me.
> > >
> > > temporal: More straightforward algorithm. Tries to achieve the goal
> > > as fast as possible, using maximum allowed quota, but only for a
> > > temporal short time. ---> When the quota is under-achieved, this
> > > algorithm keeps tuning quota to a maximum allowed one. Once the
> > > quota is [over]-achieved <---, this sets the quota zero. Useful for
> > > deterministic control required environments.
> > >
> > > I'm not sure if "goal" was accidentally written as "quota" here. Would
> > > this be better?
> > >
> > > When the goal is under-achieved, this algorithm keeps tuning quota
> > > to a maximum allowed one. Once the goal is [over-]achieved, [...]
> >
> > Good eyes! Yes, seems it was only mistakenly written in the way. Please feel
> > free to send a separate patch or include it into the next version of this
> > patch, whatever better for you.
>
> I will send a separate patch.
Makes sense to me.
[...]
> > I think the clarification is better to be added to the 'temporal' quota tuner,
> > since this happens only when it is used. Maybe the clarification could also be
> > shorter. For example,
[...]
> I agree that would be better. Although users might look up the
> definition of qt_exceeds first, they are also likely to navigate
> directly to the temporal section.
>
> I will clarify at the temporal section in the next revision.
Thank you. Looking forward to patches.
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-09-10 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 17:50 Liew Rui Yan
2026-09-09 0:38 ` SJ Park
2026-09-09 10:07 ` Liew Rui Yan
2026-09-10 0:17 ` SJ Park [this message]
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=20260910001747.110260-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aethernet65535@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@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
all inboxes | Powered by JetHome®