Linux Kernel Summit discussions
 help / color / mirror / Atom feed

From: SeongJae Park <sj@kernel.org>
To: ksummit@lists.linux.dev
Cc: sj@kernel.org, inux-mm@kvack.org, damon@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: [TECH TOPIC] DAMON: Current Status and Future Plans
Date: Wed, 26 Jul 2023 19:09:26 +0000	[thread overview]
Message-ID: <20230726190926.85121-1-sj@kernel.org> (raw)

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).  A service provider reported that they are showing about a 16%
reduction in memory usages with modest overhead on their products by utilizing
a DAMON-based system operation scheme.

After its initial introduction[3], it has continued to develop in response to
the voices from the users and kernel hackers.  We also proactively tried to get
more feedback by sharing the status and discussing future works in multiple
venues including every kernel summits since 2019[3,4,5,6] and DAMON
community[7,8].  As a result, DAMON made substantial improvements while the
list for future works never emptied.

This talk will aim to continue the sharing and discussion at the kernel summit
of 2023.  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:

- Efficient ABI and a convenient user-space tool
- Fine-grained DAMOS control
- Partial self-tuning of DAMOS
- Extension of DAMON monitoring targets
- Plan for collaborative memory-overcommit VM system management
- Plan for tiered-memory management
- Plan for DAMON accuracy improvement

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] DAMON mailing list, https://lore.kernel.org/damon
[8] DAMON meetup, https://lore.kernel.org/damon/20220810225102.124459-1-sj@kernel.org/


Thanks,
SJ

                 reply	other threads:[~2023-07-26 19:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).