From: SeongJae Park <sj@kernel.org>
To: zuoze <zuoze1@huawei.com>
Cc: SeongJae Park <sj@kernel.org>,
akpm@linux-foundation.org, damon@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
wangkefeng.wang@huawei.com
Subject: Re: [RFC PATCH] mm/damon: add full LPAE support for memory monitoring above 4GB
Date: Tue, 22 Apr 2025 10:43:01 -0700 [thread overview]
Message-ID: <20250422174301.58953-1-sj@kernel.org> (raw)
In-Reply-To: <68043882-1878-4cca-a8fc-5e6cb9a88395@huawei.com>
On Tue, 22 Apr 2025 19:50:11 +0800 zuoze <zuoze1@huawei.com> wrote:
[...]
> Thanks for the patches - I’ve noted the RFC series and user-space
> updates. Apologies for the delay; I’ll prioritize reviewing these soon
> to verify they meet the intended tracking goals. Appreciate your
> patience.
No worry. Please take your time and let me know if there is anything I can
help.
I think we can improve the user-space tool support better for usability. For
example, it could find LPAE case, set addr_unit parameter, and convert
user-input and output address ranges on its own. But hopefully the current
support allows simple tests of the kernel side change, and we could do such
improvement after the kernel side change is made.
Thanks,
SJ
[...]
next prev parent reply other threads:[~2025-04-22 17:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 7:55 [RFC PATCH] mm/damon: add full LPAE support for memory monitoring above 4GB Ze Zuo
2025-04-09 2:50 ` SeongJae Park
2025-04-09 7:01 ` zuoze
2025-04-09 17:36 ` SeongJae Park
2025-04-10 6:28 ` zuoze
2025-04-10 22:25 ` SeongJae Park
2025-04-11 6:30 ` zuoze
2025-04-11 16:35 ` SeongJae Park
2025-04-14 1:21 ` zuoze
2025-04-20 16:27 ` SeongJae Park
2025-04-22 11:50 ` zuoze
2025-04-22 17:43 ` SeongJae Park [this message]
2025-07-25 3:15 ` zuoze
2025-07-25 20:22 ` SeongJae Park
2025-07-26 3:14 ` Quanmin Yan
2025-07-26 17:16 ` SeongJae Park
2025-07-29 13:52 ` Quanmin Yan
2025-07-29 15:53 ` 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=20250422174301.58953-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wangkefeng.wang@huawei.com \
--cc=zuoze1@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).