linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: Gregory Price <gourry@gourry.net>,
	Matthew Wilcox <willy@infradead.org>,
	lsf-pc@lists.linux-foundation.org, damon@lists.linux.dev,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com, Raghavendra K T <raghavendra.kt@amd.com>,
	Yuanchu Xie <yuanchu@google.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Kaiyang Zhao <kaiyang2@cs.cmu.edu>,
	Jiaming Yan <jiamingy@amazon.com>,
	Honggyu Kim <honggyu.kim@sk.com>
Subject: Re: [LSF/MM/BPF TOPIC] DAMON Requirements for Access-aware MM of Future
Date: Thu,  2 Jan 2025 10:04:39 -0800	[thread overview]
Message-ID: <20250102180439.45429-1-sj@kernel.org> (raw)
In-Reply-To: <20250102180019.45333-1-sj@kernel.org>

On Thu, 2 Jan 2025 10:00:19 -0800 SeongJae Park <sj@kernel.org> wrote:

> On Thu, 2 Jan 2025 10:22:14 -0500 Gregory Price <gourry@gourry.net> wrote:
> 
> > On Thu, Jan 02, 2025 at 04:09:38AM +0000, Matthew Wilcox wrote:
> > > On Wed, Jan 01, 2025 at 02:20:39PM -0800, SeongJae Park wrote:
> > > > Hi all,
> > > > 
> > > > 
> > > > I find a few interesting and promising projects that aim to do efficient access
> > > > pattern-aware memory management of near future, including below (alphabetically
> > > > sorted).
> > > > 
> > > > - CXL hotness monitoring unit
> > > >   (https://lore.kernel.org/20241121101845.1815660-1-Jonathan.Cameron@huawei.com)
> > > > - Memory tiering fainess by per-cgroup control of promotion and demotion
> > > >   (https://lore.kernel.org/20241108190152.3587484-1-kaiyang2@cs.cmu.edu)
> > > > - Promotion of unmapped page cache folios
> > > >   (https://lore.kernel.org/20241210213744.2968-1-gourry@gourry.net)
> > > 
> > > I'm not sure how DAMON can help with this one.  As I understand DAMON,
> > > it monitors accesses to user addresses.  This patchset is trying to solve
> > > the problem for file pages which aren't mapped to userspace at all.
> > > ie only accessed through read() and write().
> > 
> > DAMON can monitor physical addresses to, though the mechanism is
> > different.
> 
> Thank you for answering this, Gregory.  As Gregory explained, users can use
> physical address monitoring mode of DAMON for this.  For unmapped pages, DAMON
> sets and reads PG_idle to check if it is accessed or not.  Since PG_idle is
> respected by read() and write() use case to my understanding, DAMON should be
> able to check accesses to unmapped pages.
> 
> > I haven't assessed this as a solution, yet.
> 
> To quickly see this, I ran below simple test.
[...]
> the point of this test is that DAMON at least somehow react to accesses for
> unmapped pages.

Forgot clarifying this point, sorry.  My test shows DAMON can detect accesses
to unmapped pages, but not asseses if it is feasible as the unmapped pages
promotion solution.  More works and discussions would be needed for that.


Thanks,
SJ

[...]


  reply	other threads:[~2025-01-02 18:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-01 22:20 SeongJae Park
2025-01-02  4:09 ` Matthew Wilcox
2025-01-02 15:22   ` Gregory Price
2025-01-02 18:00     ` SeongJae Park
2025-01-02 18:04       ` SeongJae Park [this message]
2025-01-14  3:06 ` Gregory Price
2025-01-24  2:11   ` SeongJae Park
2025-01-24 17:21     ` Gregory Price
2025-01-25  1:17       ` SeongJae Park
2025-01-30  2:15   ` Yuanchu Xie
2025-01-30  3:47     ` SeongJae Park
2025-01-31 10:05       ` Jonathan Cameron
2025-01-20 18:46 ` Jonathan Cameron
2025-03-25 21:01 ` SeongJae Park

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=20250102180439.45429-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=damon@lists.linux.dev \
    --cc=gourry@gourry.net \
    --cc=honggyu.kim@sk.com \
    --cc=jiamingy@amazon.com \
    --cc=kaiyang2@cs.cmu.edu \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=raghavendra.kt@amd.com \
    --cc=willy@infradead.org \
    --cc=yuanchu@google.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