From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: 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>,
Gregory Price <gourry@gourry.net>,
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: Tue, 25 Mar 2025 14:01:13 -0700 [thread overview]
Message-ID: <20250325210114.844509-1-sj@kernel.org> (raw)
In-Reply-To: <20250101222039.74565-1-sj@kernel.org>
Hello,
On Wed, 1 Jan 2025 14:20:39 -0800 SeongJae Park <sj@kernel.org> 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)
> - Slow-tier page promotion based on PTE A bit
> (https://lore.kernel.org/20241201153818.2633616-1-raghavendra.kt@amd.com)
> - Workingset reporting
> (https://lore.kernel.org/20241127025728.3689245-1-yuanchu@google.com)
>
> The goal of DAMON is to help accelerating such developments by being a
> framework that can reduce fundamental efforts for monitoring memory access
> patterns and managing memory using the information. AWS Aurora Serverless v2
> and SK hynix are successfully using DAMON in the way for proactive memory
> reclamation[1] and CXL memory tiering[2].
>
> To further deliver such benefits for the ongoing and future projects, we need
> to better understand what the projects really need, how DAMON can provide those
> now or in future, and if there are alternatives better than DAMON. Regardless
> of the conclusion about DAMON, the works apparently have common parts, so the
> discussion will benefit all.
>
> I propose to have the discussion at LSF/MM/BPF. In the session, I will briefly
> introduce the works and possible DAMON usages, and continue the open discussion
> for better understanding each other. The discussion will not be limited to
> DAMON and abovely mentioned projects but possible alternatives and general
> access-aware memory management projects. After the discussion, we will
> hopefully find ways to efficiently collaborate, or at least do not disturb each
> other.
>
> [1] https://assets.amazon.science/ee/a4/41ff11374f2f865e5e24de11bd17/resource-management-in-aurora-serverless.pdf
> [2] https://github.com/skhynix/hmsdk/wiki/Capacity-Expansion
A draft of the slides for this session is now available at
https://github.com/damonitor/talks/blob/master/2025/lsfmmbpf/damon_requirements_lsfmmbpf_2025.pdf
I may make more last time changes to the slides, but the final version should
also be available on the same URL.
Thanks,
SJ
[...]
prev parent reply other threads:[~2025-03-25 21:01 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
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 [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=20250325210114.844509-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=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