linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: "Pulavarty, Badari" <badari.pulavarty@intel.com>
Cc: SeongJae Park <sj@kernel.org>,
	"lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"damon@lists.linux.dev" <damon@lists.linux.dev>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [LSF/MM/BPF TOPIC] DAMON Updates and Future Plans
Date: Wed,  1 Mar 2023 00:55:21 +0000	[thread overview]
Message-ID: <20230301005521.78027-1-sj@kernel.org> (raw)
In-Reply-To: <DM6PR11MB397833DB2DF869EB50D5E92F9CAD9@DM6PR11MB3978.namprd11.prod.outlook.com>

Hi Badari,

On Wed, 1 Mar 2023 00:24:54 +0000 "Pulavarty, Badari" <badari.pulavarty@intel.com> wrote:

> Hi SJ,
> 
> We discussed this earlier. 
> 
> - Are there plans to make DAMON monitor/manage cgroup instead of individual pids? 

Yes.

For moniroting cgroups, there are only rough ideas at the moment, and no much
progress has made so far.  I hope to discuss about real needs of this feature
(I didn't make much progress here mainly because there was no many people
pushing this) and the best way for implementing it during the session if
possible.

For monitoring-based memory management of cgroups (via DAMOS), however, DAMOS
provides cgroup-based management action target memory filtering[1].  Using the
feature, you can do cgroups-based access-aware memory management.  The patchset
has merged into the mainline a few days ago.

[1] https://lore.kernel.org/damon/20221205230830.144349-1-sj@kernel.org/


Thanks,
SJ

> 
> Thanks,
> Badari
> 
> -----Original Message-----
> From: SeongJae Park <sj@kernel.org> 
> Sent: Monday, February 13, 2023 4:33 PM
> To: lsf-pc@lists.linux-foundation.org
> Cc: SeongJae Park <sj@kernel.org>; damon@lists.linux.dev; linux-mm@kvack.org; linux-kernel@vger.kernel.org
> Subject: [LSF/MM/BPF TOPIC] DAMON Updates and Future Plans
> 
> 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.
> 
> 
> Thanks,
> SJ
> 


  reply	other threads:[~2023-03-01  0:55 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 [this message]
2023-05-08 21:40 ` SeongJae Park
2023-05-13 14:53   ` SeongJae Park

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=20230301005521.78027-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=badari.pulavarty@intel.com \
    --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).