linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: SeongJae Park <sj@kernel.org>
Cc: ksummit@lists.linux.dev, damon@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Fwd: [TECH TOPIC] DAMON: Updates and Plans
Date: Fri, 14 Jun 2024 11:42:45 -0700	[thread overview]
Message-ID: <20240614184245.88080-1-sj@kernel.org> (raw)
In-Reply-To: <20240614175504.87365-1-sj@kernel.org>

I made a typo on the mail address for linux-mm@, on the original mail.  So
forwarding to linux-mm@ as a reply-to-all.  Sorry for making noise.

================================= >8 ========================================

Hello all,


I'm posting my Kernel Summit topic suggestion below.  I will also submit it to
the LPC site.


DAMON[1,2] is a Linux kernel subsystem that provides efficient data access
monitoring and access-aware system operations (DAMON-based Operation Schemes,
a.k.a DAMOS).  From multiple use cases of it including multiple years of real
world products' usage, it is proven to be useful for improving memory
efficiency.

Like many other Linux kernel projects, DAMON is developed by the community.  We
proactively present the status and discuss future plans of DAMON with the
community.  As a major part of the effort, we had a DAMON session every year at
Kernel Summit[3-7].  Those sessions have been one of the most essential and
effectful fuels of the project.

This session will continue the sharing and discussion at the kernel summit of
2024.  We will share what feedback we received, what patches have been
developed or are under development, what requests are still in the planning
stage, and what the plans are.  With that, hopefully we will have discussions
that will be helpful for improving and prioritizing the plans and specific
tasks, and finding new requirements.

Specific sub-topics would include, but are not limited to:

- Fine-grained DAMOS control
- Automated tuning of DAMOS
- Tiered-memory management
- Access/Contiguity-aware Memory Auto-scaling
- Write-only monitoring and live migration

Based on the progress until the summit, some items can be added or dropped.

[1] project homepage, https://damonitor.github.io
[2] official doc, https://docs.kernel.org/mm/damon/index.html
[3] ksummit 2019, https://linuxplumbersconf.org/event/4/contributions/548/
[4] ksummit 2020, https://www.linuxplumbersconf.org/event/7/contributions/659/
[5] ksummit 2021, https://linuxplumbersconf.org/event/11/contributions/984/
[6] ksummit 2022, https://lpc.events/event/16/contributions/1224/
[7] ksummit 2023, https://lpc.events/event/17/contributions/1624/


Thanks,
SJ


           reply	other threads:[~2024-06-14 18:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240614175504.87365-1-sj@kernel.org>]

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=20240614184245.88080-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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