From: "Kunwu Chan" <kunwu.chan@linux.dev>
To: "SeongJae Park" <sj@kernel.org>
Cc: "SeongJae Park" <sj@kernel.org>,
"Kunwu Chan" <chentao@kylinos.cn>,
"Wang Lian" <lianux.mm@gmail.com>,
akpm@linux-foundation.org, damon@lists.linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/damon: fix stale TLB young-state handling on arm64
Date: Mon, 01 Jun 2026 02:09:37 +0000 [thread overview]
Message-ID: <1d19bb24fe6c1f6935ef078f7d7461e73590f21c@linux.dev> (raw)
In-Reply-To: <20260531162457.98724-1-sj@kernel.org>
June 1, 2026 at 12:24 AM, "SeongJae Park" <sj@kernel.org mailto:sj@kernel.org?to=%22SeongJae%20Park%22%20%3Csj%40kernel.org%3E > wrote:
>
> On Sun, 31 May 2026 12:16:49 +0000 "Kunwu Chan" <kunwu.chan@linux.dev> wrote:
>
> [...]
>
> >
> > We think that makes sense. Explaining the rationale for not flushing TLB,
> > the limitations this can introduce for tests, and recommendations for
> > choosing reliable test working set sizes would be helpful.
> >
> Thank you for kindly accepting my suggestion.
>
Thanks, SJ.
> >
> > If we later find cases where the documented recommendations are still
> > insufficient, we can revisit more intrusive approaches.
> >
> > I'd be happy to help with the documentation work if needed. Please let
> > me know if you'd like me to prepare a draft patch.
> >
> Yes, please feel free to send a patch! :)
>
Will send it once I have something ready.
Thanks, Kunwu
> Thanks,
> SJ
>
> [...]
>
prev parent reply other threads:[~2026-06-01 2:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 14:48 [PATCH] mm/damon: fix stale TLB young-state handling on arm64 Kunwu Chan
2026-05-25 15:34 ` sashiko-bot
2026-05-25 17:46 ` SeongJae Park
2026-05-26 8:57 ` Kunwu Chan
2026-05-26 14:50 ` SeongJae Park
2026-05-31 12:16 ` Kunwu Chan
2026-05-31 16:24 ` SeongJae Park
2026-06-01 2:09 ` Kunwu Chan [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=1d19bb24fe6c1f6935ef078f7d7461e73590f21c@linux.dev \
--to=kunwu.chan@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=chentao@kylinos.cn \
--cc=damon@lists.linux.dev \
--cc=lianux.mm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.