From: SJ Park <sj@kernel.org>
To: Aveline Noir <jm5905938@gmail.com>
Cc: SJ Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
damon@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Randy Dunlap <rdunlap@infradead.org>,
sashiko-bot@kernel.org, sashiko-reviews@lists.linux.dev,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [RFC PATCH v2 0/4] mm/damon: introduce age_ms damos core filter type
Date: Thu, 5 Nov 2026 06:32:45 -0800 [thread overview]
Message-ID: <20261105143246.91656-1-sj@kernel.org> (raw)
In-Reply-To: <179388191315.401969.13923237674993632654.b4-reply@b4>
On Thu, 05 Nov 2026 23:31:53 +1100 Aveline Noir <jm5905938@gmail.com> wrote:
> Hi SJ,
>
> On Wed, 04 Nov 2026 20:44:20 -0800 SJ Park wrote:
>
> > One straightforward solution is extending the DAMOS access pattern for
> > specific deterministic time based age specification. However, DAMOS
> > core filter is a better option. It is playing a similar role in a more
> > flexible way.
>
> Makes sense.
>
> Reviewed-by: Aveline Noir <jm5905938@gmail.com>
Thank you for reviewing, Aveline!
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-11-05 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 4:44 SJ Park
2026-11-05 4:44 ` [RFC PATCH v2 1/4] mm/damon/core: add DAMOS_FILTER_TYPE_AGE_MS SJ Park
2026-11-05 4:44 ` [RFC PATCH v2 2/4] mm/damon/sysfs-schemes: support DAMOS_FILTER_TYPE_AGE_MS SJ Park
2026-11-05 4:44 ` [RFC PATCH v2 3/4] Docs/mm/damon/design: update for age_ms damos core filter type SJ Park
2026-11-05 4:44 ` [RFC PATCH v2 4/4] Docs/admin-guide/mm/damon/usage: update for age_ms damos core filter SJ Park
2026-11-05 12:31 ` [RFC PATCH v2 0/4] mm/damon: introduce age_ms damos core filter type Aveline Noir
2026-11-05 14:32 ` 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=20261105143246.91656-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=jm5905938@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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
all inboxes | Powered by JetHome®