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
Subject: Re: [LSF/MM/BPF TOPIC] DAMON Updates and Future Plans
Date: Sat, 13 May 2023 14:53:14 +0000 [thread overview]
Message-ID: <20230513145314.84505-1-sj@kernel.org> (raw)
In-Reply-To: <20230508214019.80558-1-sj@kernel.org>
On Mon, 8 May 2023 21:40:19 +0000 SeongJae Park <sj@kernel.org> wrote:
> Hello,
>
> On Tue, 14 Feb 2023 00:33:28 +0000 SeongJae Park <sj@kernel.org> wrote:
>
> > Hi all,
> >
> >
> > DAMON has merged into mainline as a data access monitoring tool that equips a
> > best-effort overhead-accuracy tradeoff mechanism, and then extended for data
> > access-aware system operations. I'd like to briefly introduce current state of
> > DAMON and share/discuss about 2023 plans including below.
> >
> > - Finer and easier-to-use DAMOS tuning
> > - tuning aggressiveness based on user or kernel feed (e.g., QPS or PSI)
> > - Merging DAMON user space tool into the mainline
> > - Extending DAMON
> > - Page-granularity monitoring
> > - LRU-lists based page-granulariy monitoring
> > - CPU-specific access monitoring
> > - Read/Write-only access monitoring
> > - More DAMON-based Operation Schemes
> > - Tiered memory management
> > - THP memory footprint reduction
> > - NUMA balancing
> >
> > I hope to hear concerns/interests about the plans for prioritizing each work
> > items and get some suggestions of future works and collaboration with other
> > kernel subsystems/hackers.
>
> We will start the discussion after about 1 hour and 20 minutes, so sharing the
> slides here:
> https://drive.google.com/file/d/10nsd4fq01On9p-oTmCS5KSW6qESmB6ER/view?usp=sharing
>
> The link might be changed later. I will update on this thread in the case.
As mentioned above, I indeed moved it to Github[1]. Above Google Drive link
may be expired soon.
[1] https://github.com/damonitor/talks/blob/master/2023/lsfmmbpf/damon_lsfmmbpf_2023.pdf
Thanks,
SJ
>
>
> Thanks,
> SJ
>
> >
> >
> > Thanks,
> > SJ
> >
prev parent reply other threads:[~2023-05-13 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 0:33 [LSF/MM/BPF TOPIC] DAMON Updates and Future Plans SeongJae Park
2023-03-01 0:24 ` Pulavarty, Badari
2023-03-01 0:55 ` SeongJae Park
2023-05-08 21:40 ` SeongJae Park
2023-05-13 14:53 ` 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=20230513145314.84505-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).