[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250729183459.56512-1-sj@kernel.org>
Date: Tue, 29 Jul 2025 11:34:59 -0700
From: SeongJae Park <sj@...nel.org>
To: Yueyang Pan <pyyjason@...il.com>
Cc: SeongJae Park <sj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Usama Arif <usamaarif642@...il.com>,
damon@...ts.linux.dev,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 0/2] mm/damon: Add damos_stat support for vaddr
Hello Pan (Or, should I call you Yueyang or Jason? Please let me know your
preferrence if you have),
On Tue, 29 Jul 2025 06:53:28 -0700 Yueyang Pan <pyyjason@...il.com> wrote:
> From: PanJason <pyyjason@...il.com>
>
> Previously damos_stat only supoort paddr. This patch set adds support
> for damos_stat for vaddr. Also all different types of filters are
> supported.
>
> Functionality Test
> ==================
> I wrote a small test program which allocates 10GB of DRAM, use
> madvise(MADV_HUGEPAGE) to convert the base pages to 2MB huge pages
> Then my program does the following things in order:
> 1. Write sequentially to the whole 10GB region
> 2. Read the first 5GB region sequentially for 10 times
> 3. Sleep 5s
> 4. Read the second 5GB region sequentially for 10 times
>
> With a proper damon setting, we are expected to see df-passed to be 10GB
> and hot region move around with the read
>
> $ # Start damon record
> $sudo ./damo/damo record "./my_test/test" --monitoring_intervals 100000\
> 1000000 2000000
You can use 'start' instead of 'record' for this test purpose.
--monitoring_intervals receive more human-friendly format, so you can do
'--monitoring_intervals 100ms 1s 2s'.
>
> $ # damon report
> $sudo ./damo/damo report access --snapshot_damos_filter reject none \
> hugepage_size 2MiB 2MiB
The --snapshot_damos_filter option means you want to make folios that not
having size 2 MiB not passed by the filter. You can ask same thing in more
intuitive way, like below.
--snapshot_damos_filter allow hugepage_size 2MiB 2MiB
> heatmap:
> # min/max temperatures: -900,000,000, 100,002,000, column size: 136.564 MiB
checkpatch.pl gives me below warning:
WARNING: Commit log lines starting with '#' are dropped by git as comments
I'd suggest adding four spaces prefix to quoted command outputs like this.
> intervals: sample 100 ms aggr 1 s (max access hz 10)
> # damos filters (df): reject none hugepage_size [2.000 MiB, 2.000 MiB]
> df-pass:
> # min/max temperatures: -663,075,528, 100,002,000, column size: 128.037 MiB
> 0 addr 86.082 TiB size 682.039 MiB access 0 hz age 9 s df-passed 0 B
> 1 addr 127.225 TiB size 466.039 MiB access 1.000 hz age 0 ns df-passed 468.000 MiB
[...]
> memory bw estimate: 3.615 GiB per second df-passed: 3.615 GiB per second
> total size: 10.669 GiB df-passed 10.000 GiB
> record DAMON intervals: sample 100 ms, aggr 1 s
>
> $ # damon report again
> $sudo ./damo/damo report access --snapshot_damos_filter reject none \
> hugepage_size 2MiB 2MiB
> heatmap:
> # min/max temperatures: -1,100,000,000, 300,001,000, column size: 136.564 MiB
> intervals: sample 100 ms aggr 1 s (max access hz 10)
> # damos filters (df): reject none hugepage_size [2.000 MiB, 2.000 MiB]
> df-pass:
> # min/max temperatures: -800,000,000, 300,001,000, column size: 128.037 MiB
> 0 addr 86.082 TiB size 682.039 MiB access 0 hz age 11 s df-passed 0 B
> 1 addr 127.225 TiB size 10.355 MiB access 1.000 hz age 0 ns df-passed 12.000 MiB
> 2 addr 127.225 TiB size 93.207 MiB access 1.000 hz age 0 ns df-passed 92.000 MiB
> 3 addr 127.225 TiB size 414.262 MiB access 1.000 hz age 0 ns df-passed 414.000 MiB
> 4 addr 127.225 TiB size 706.695 MiB access 1.000 hz age 3 s df-passed 708.000 MiB
> 5 addr 127.226 TiB size 78.523 MiB access 1.000 hz age 3 s df-passed 78.000 MiB
[...]
> total size: 10.669 GiB df-passed 10.000 GiB
> record DAMON intervals: sample 100 ms, aggr 1 s
>
> As you can see the total df-passed region is 10GiB and the hot region
> moves as the seq read keeps going
>
> PanJason (2):
> mm/damon: Move invalid folio and has filter to ops-common
> mm/damon: Add damos_stat support for vaddr
The changes look good overall, though I left a few comments for formatting and
unnecessary folio references that inherited from my original sin. Looking
forward to more discussions and next version of this great patch series!
Thanks,
SJ
[...]
Powered by blists - more mailing lists