From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Aveline Noir <jm5905938@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
damon@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Ravi Jonnalagadda <ravis.opensrc@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [RFC PATCH v0] Docs/mm/damon/design: document data attributes report infra design (beyond page table accessed-bit milestone 2)
Date: Wed, 11 Nov 2026 11:17:51 -0800 [thread overview]
Message-ID: <20261111191752.145919-1-sj@kernel.org> (raw)
In-Reply-To: <20261111185412.145514-1-sj@kernel.org>
On Wed, 11 Nov 2026 10:54:11 -0800 SJ Park <sj@kernel.org> wrote:
> Hi Aveline,
>
> On Wed, 11 Nov 2026 18:35:52 +1100 Aveline Noir <jm5905938@gmail.com> wrote:
>
> > 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.
>
> Thank you for sharing this finding. Seems this theory assumes the probe will
> hit for report of any byte of the region exists in the report buffers. Under
> the assumption, that makes sense.
>
> But I'd say the assumed implementation is not realistic. That's because DAMON
> design does probing for only single sampling byte of the region, not the entire
> bytes of the region. In a real implementation that is aligned with the design,
> the probe will hit if a report associated with the sampling byte exists.
I will rephrase the document in the next spin to make this be more clear.
E.g., The probes can be configured to hit for existence of specific types of
reports that associated with the probing memory in the report buffers.
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-11-11 19:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 19:57 SJ Park
2026-10-22 4:17 ` Ravi Jonnalagadda
2026-10-22 5:29 ` SJ Park
2026-10-23 19:51 ` Ravi Jonnalagadda
2026-10-24 0:42 ` SJ Park
2026-11-01 18:34 ` SJ Park
2026-11-11 7:35 ` Aveline Noir
2026-11-11 18:54 ` SJ Park
2026-11-11 19:17 ` SJ Park [this message]
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=20261111191752.145919-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=jm5905938@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ravis.opensrc@gmail.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
/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
all inboxes | Powered by JetHome®