Re: [RFC PATCH v0] Docs/mm/damon/design: document data attributes report infra design (beyond page table accessed-bit milestone 2)

From: Aveline Noir

Date: Wed Nov 11 2026 - 02:40:42 EST


Hi SJ,

On Sat, 17 Oct 2026 12:57:45 -0700 SJ Park wrote:

> +The data attribute probe supports the reports. The probes can be configured to
> +hit for a given memory region depending on the existence of specific types of
> +reports that associated with the memory region in given report buffers.

I'm wondering how this would interact with the region size. If each
page of a region is reported with probability q, a region of s pages
would hit with probability 1 - (1 - q)^s, so a large region may hit
more often than a small region of the same access density. The page
table accessed-bit check samples one page per region, so its hit rate
doesn't depend on the region size in the same way.

A quick replay of the crediting rule of Ravi's RFC v4 [1] on synthetic
traces showed a similar trend. The adaptive regions adjustment would
mitigate this to some extent, but large cold-only regions still kept
high hit rates after split and merge in the replay. I'm not sure how
much it matters on real workloads, though.

Would crediting the hits relative to the region size, e.g., reported
bytes / region bytes, make sense to you? It would need probe_hits
wider than u8, so it is not free. If you think it is worth exploring,
I may run more experiments and share the results.

[1] https://lore.kernel.org/all/20261005-damon-perf-rfc-v3-send-2026-10-03-v4-0-b03452e137f3@xxxxxxxxx/

Thanks,
Aveline Noir