From: SeongJae Park <sj@kernel.org>
To: Xin Hao <xhao@linux.alibaba.com>
Cc: sjpark@amazon.de, akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/damon/dbgfs: add region_stat interface
Date: Tue, 12 Oct 2021 07:11:19 +0000 [thread overview]
Message-ID: <20211012071119.32320-1-sj@kernel.org> (raw)
In-Reply-To: <20211012054948.90381-1-xhao@linux.alibaba.com>
Hello Xin, thank you for this patch!
On Tue, 12 Oct 2021 13:49:48 +0800 Xin Hao <xhao@linux.alibaba.com> wrote:
> Using damon-dbgfs has brought great convenience to user-mode
> operation damon, but sometimes if i want to be able to view
> the division of task regions, nr_access values etc,but i found
> that it is impossible to view directly through the dbgfs interface,
> so there i add a interface "region_stat", it displays like this.
>
> # cat region_stat
> last_aggregation=120.87s
> target_id=5148
> nr_regions=10
> 400000-258c000(34352 KiB): 1
> 258c000-4719000(34356 KiB): 0
> 4719000-abbf000(103064 KiB): 0
> abbf000-c4d4000(25684 KiB): 11
> c4d4000-ff5c000(59936 KiB): 15
> ff5c000-152f9000(85620 KiB): 20
> 152f9000-1599e000(6804 KiB): 10
> 1599e000-19573000(61268 KiB): 0
> 19573000-1f92c000(102116 KiB): 0
> 1f92c000-22a4c000(50304 KiB): 0
I think similar information could also be collected via the 'damon_aggregated'
tracepoint[1], which is merged in the mainline, or 'DAMOS_STAT'[2], which is
merged in -mm. The recording feature[3] could also be used, though it would
take some time before it is merged in the mainline. Have you considered using
those but found some problem?
[1] https://git.kernel.org/torvalds/c/2fcb93629ad8
[2] https://lore.kernel.org/linux-mm/20211001125604.29660-6-sj@kernel.org/
[3] https://lore.kernel.org/linux-mm/20211008094509.16179-1-sj@kernel.org/
Thanks,
SJ
[...]
next prev parent reply other threads:[~2021-10-12 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 5:49 Xin Hao
2021-10-12 7:11 ` SeongJae Park [this message]
2021-10-12 7:57 ` Xin Hao
2021-10-12 9:37 ` SeongJae Park
2021-10-12 17:16 ` kernel test robot
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=20211012071119.32320-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sjpark@amazon.de \
--cc=xhao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox