From: "Shah, Amit" <aams@amazon.de>
To: "sj38.park@gmail.com" <sj38.park@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "david@redhat.com" <david@redhat.com>,
"rientjes@google.com" <rientjes@google.com>,
"acme@kernel.org" <acme@kernel.org>,
"snu@amazon.de" <snu@amazon.de>,
"peterz@infradead.org" <peterz@infradead.org>,
"minchan@kernel.org" <minchan@kernel.org>,
"vdavydov.dev@gmail.com" <vdavydov.dev@gmail.com>,
"linux-damon@amazon.com" <linux-damon@amazon.com>,
"zgf574564920@gmail.com" <zgf574564920@gmail.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"fan.du@intel.com" <fan.du@intel.com>,
"Park, Seongjae" <sjpark@amazon.de>,
"amit@kernel.org" <amit@kernel.org>,
"gthelen@google.com" <gthelen@google.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"shuah@kernel.org" <shuah@kernel.org>,
"Foerster, Leonard" <foersleo@amazon.de>,
"guoju.fgj@alibaba-inc.com" <guoju.fgj@alibaba-inc.com>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"shakeelb@google.com" <shakeelb@google.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"greg@kroah.com" <greg@kroah.com>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"rppt@kernel.org" <rppt@kernel.org>,
"mgorman@suse.de" <mgorman@suse.de>,
"Jonathan.Cameron@Huawei.com" <Jonathan.Cameron@Huawei.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"brendanhiggins@google.com" <brendanhiggins@google.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"elver@google.com" <elver@google.com>,
"riel@surriel.com" <riel@surriel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v29 00/13] Introduce Data Access MONitor (DAMON)
Date: Fri, 21 May 2021 08:55:18 +0000 [thread overview]
Message-ID: <c273f5a8797a6c00c8ce004b0979961873d4fcf0.camel@amazon.com> (raw)
In-Reply-To: <20210520153426.34bfe5ab64ca1f06cca6f231@linux-foundation.org>
Hey Andrew,
On Thu, 2021-05-20 at 15:34 -0700, Andrew Morton wrote:
> Thanks for persisting with this.
>
> I'd be interested in people's overall take on this work, please.
> Mainly a high-level "should we merge this" view. Detailed review of
> implementation and interface details can follow on in the usual fashion.
There are a few kernel developers at Amazon watching over this effort,
and nudging it along. But more importantly, we're working with fleet
owners operating large fleets to guide this effort.
That makes the overall effort a 2-phase one: profiling first (which is
what this patchset does), and then improving other things that use this
profiling information for better system efficiencies.
All that's primarily for use-cases internally right now. Once the base
set of patches is upstream, we're going to work on all the various use-
cases we've identified so far where this is going to be beneficial.
Current internal uses are mainly around profiling. One example is
mentioned by SeongJae in the cover letter's "Real-world User Story"
section, where tuning page reclamation algorithms based on this
profiling information is going to result in better efficiencies, and
energy and cost reductions.
Another interesting usecase that's developing is identifying free pages
for reclamation and compaction based on this work. That's going to
help live migration and memory overcommit scenarios for KVM guests. SJ
is preparing to send out those patches to the lists as well.
Thanks!
Amit
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next prev parent reply other threads:[~2021-05-21 8:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 7:56 [PATCH v29 00/13] Introduce Data Access MONitor (DAMON) SeongJae Park
2021-05-20 7:56 ` [PATCH v29 01/13] mm: " SeongJae Park
2021-05-20 7:56 ` [PATCH v29 02/13] mm/damon/core: Implement region-based sampling SeongJae Park
2021-05-20 7:56 ` [PATCH v29 03/13] mm/damon: Adaptively adjust regions SeongJae Park
2021-05-25 15:17 ` sieberf
2021-05-25 15:39 ` SeongJae Park
2021-05-20 7:56 ` [PATCH v29 04/13] mm/idle_page_tracking: Make PG_idle reusable SeongJae Park
2021-06-11 12:55 ` Shah, Amit
2021-06-11 13:49 ` SeongJae Park
2021-05-20 7:56 ` [PATCH v29 05/13] mm/damon: Implement primitives for the virtual memory address spaces SeongJae Park
2021-05-25 15:19 ` sieberf
2021-05-25 15:44 ` SeongJae Park
2021-05-20 7:56 ` [PATCH v29 06/13] mm/damon: Add a tracepoint SeongJae Park
2021-05-20 7:56 ` [PATCH v29 07/13] mm/damon: Implement a debugfs-based user space interface SeongJae Park
2021-06-11 18:59 ` sieberf
2021-06-14 6:48 ` SeongJae Park
2021-05-20 7:56 ` [PATCH v29 08/13] mm/damon/dbgfs: Export kdamond pid to the user space SeongJae Park
2021-05-20 7:56 ` [PATCH v29 09/13] mm/damon/dbgfs: Support multiple contexts SeongJae Park
2021-06-14 9:30 ` sieberf
2021-06-14 9:35 ` SeongJae Park
2021-06-14 9:44 ` Greg KH
2021-05-20 7:56 ` [PATCH v29 10/13] Documentation: Add documents for DAMON SeongJae Park
2021-06-09 7:03 ` SeongJae Park
2021-06-11 17:44 ` Boehme, Markus
2021-06-11 18:53 ` SeongJae Park
2021-05-20 7:56 ` [PATCH v29 11/13] mm/damon: Add kunit tests SeongJae Park
2021-05-20 7:56 ` [PATCH v29 12/13] mm/damon: Add user space selftests SeongJae Park
2021-06-11 13:57 ` Maximilian Heyne
2021-06-11 14:04 ` SeongJae Park
2021-05-20 7:56 ` [PATCH v29 13/13] MAINTAINERS: Update for DAMON SeongJae Park
2021-05-20 22:34 ` [PATCH v29 00/13] Introduce Data Access MONitor (DAMON) Andrew Morton
2021-05-21 2:53 ` Shakeel Butt
2021-05-21 8:55 ` Shah, Amit [this message]
2021-06-14 8:09 ` sieberf
2021-06-15 16:30 ` sieberf
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=c273f5a8797a6c00c8ce004b0979961873d4fcf0.camel@amazon.com \
--to=aams@amazon.de \
--cc=Jonathan.Cameron@Huawei.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=amit@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dwmw@amazon.co.uk \
--cc=elver@google.com \
--cc=fan.du@intel.com \
--cc=foersleo@amazon.de \
--cc=greg@kroah.com \
--cc=gthelen@google.com \
--cc=guoju.fgj@alibaba-inc.com \
--cc=linux-damon@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=shakeelb@google.com \
--cc=shuah@kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.de \
--cc=snu@amazon.de \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=zgf574564920@gmail.com \
/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).