From: SeongJae Park <sj@kernel.org>
To: Rongwei Wang <rongwei.wang@linux.alibaba.com>
Cc: sj@kernel.org, akpm@linux-foundation.org, linux-damon@amazon.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] mm/damon/sysfs: support fixed virtual address ranges monitoring
Date: Mon, 2 May 2022 16:18:10 +0000 [thread overview]
Message-ID: <20220502161810.134199-1-sj@kernel.org> (raw)
In-Reply-To: <80586516-d783-8f81-f6d7-338d9af7a3e6@linux.alibaba.com>
Hi Rongwei,
On Mon, 2 May 2022 15:56:58 +0800 Rongwei Wang <rongwei.wang@linux.alibaba.com> wrote:
> Hi, SeongJae
>
> I had read and tested your patchset these days. It works.
Thank you for the tests! :D
> It seems that these patches only fix the issue about init_regions in
> DAMON-sysfs, but not fix in DAMON-dbgfs? maybe I missing something.
>
> If so, do you have any plan to fix this bug in dbgfs? Actually, what I
> want to say is that I ready a patch for solving the init_regions related
> bug in dbgfs these days. I not sure if you're interested in it.
The plan is to freeze DAMON debugfs interface after DAMON sysfs interface is
merged, and then entirely remove it after next LTS kernel. It was mentioned in
the sysfs interface patchset as below:
https://lore.kernel.org/linux-mm/20220228081314.5770-1-sj@kernel.org/
Future Plan of DAMON_DBGFS Deprecation
======================================
Once this patchset is merged, DAMON_DBGFS development will be frozen. That is,
we will maintain it to work as is now so that no users will be break. But, it
will not be extended to provide any new feature of DAMON. The support will be
continued only until next LTS release. After that, we will drop DAMON_DBGFS.
The plan was also shared in the kernel doc as below[1], but maybe it was too
small to read, or ambiguous. Sorry if it was the case.
debugfs interface. This is almost identical to sysfs interface. This will
be _removed_ after next LTS kernel is released, so users should move to the
sysfs interface.
[1] https://docs.kernel.org/admin-guide/mm/damon/usage.html#debugfs-interface
So, I don't have a big interest at extending DAMON debugfs for fvaddr. That
said, of course we could discuss more if you really need it. If so, please let
me know.
Thanks,
SJ
>
> Best Regards,
> Rongwei
>
next prev parent reply other threads:[~2022-05-02 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 23:17 [PATCH 0/3] support fixed virtual address ranges monitoring sj
2022-04-26 23:17 ` [PATCH 1/3] mm/damon/vaddr: register a damon_operations for " sj
2022-04-26 23:17 ` [PATCH 2/3] mm/damon/sysfs: support " sj
2022-05-02 7:56 ` Rongwei Wang
2022-05-02 16:18 ` SeongJae Park [this message]
2022-05-03 2:20 ` Rongwei Wang
2022-04-26 23:17 ` [PATCH 3/3] Docs/{ABI,admin-guide}/damon: update for " sj
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=20220502161810.134199-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-damon@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rongwei.wang@linux.alibaba.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 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.