ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: ksummit-discuss@lists.linuxfoundation.org, ksummit@lists.linux.dev
Cc: linux-mm@kvack.org, damon@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [TECH TOPIC] Current Status and Future Plans of DAMON
Date: Thu, 16 Jun 2022 22:43:06 +0000	[thread overview]
Message-ID: <20220616224306.92076-1-sj@kernel.org> (raw)

Hello all,

I'm posing my Kernel Summit topic suggestion as below.  I will also submit it
on LPC site.

DAMON[1] is Linux kernel's data access monitoring framework that provides
best-effort accuracy under user-specified overhead range.  It has been about
one year after it has been merged in the mainline.  Meanwhile, we received a
number of new voices for DAMON from users and made efforts for answering to
those.  Nevertheless, many things to do for that are remaining.

This talk will share what such voices we received, what patches are developed
or under development for those, what requests are still under plan only, 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 will include, but not limited to:

- Making DAMON ABI more stable and flexibile
- Extending DAMON for more usages
- Improving DAMON accuracy
- DAMON-based kernel/user space optimization policies
- Making user space DAMON policies more efficient
- Making kernel space DAMON policies just work (auto-tuning)

[1] https://damonitor.github.io


                 reply	other threads:[~2022-06-16 22:43 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220616224306.92076-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \


* 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;
as well as URLs for NNTP newsgroup(s).