From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: SeongJae Park <sjpark@amazon.com>
Cc: akpm@linux-foundation.org, SeongJae Park <sjpark@amazon.de>,
acme@kernel.org, brendan.d.gregg@gmail.com, corbet@lwn.net,
mgorman@suse.de, dwmw@amazon.com, amit@kernel.org,
rostedt@goodmis.org, sj38.park@gmail.com, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Introduce Data Access MONitor (DAMON)
Date: Mon, 20 Jan 2020 19:55:51 +0300 [thread overview]
Message-ID: <20200120165551.codmosqc2pkcunpa@box> (raw)
In-Reply-To: <20200120162757.32375-1-sjpark@amazon.com>
On Mon, Jan 20, 2020 at 05:27:49PM +0100, SeongJae Park wrote:
> This patchset introduces a new kernel module for practical monitoring of
> data accesses, namely DAMON.
Looks like it's not integrated with perf at all right? Why?
Correlating measurements from different domains would help to see the
bigger picture.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2020-01-20 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 16:27 [PATCH 0/8] Introduce Data Access MONitor (DAMON) SeongJae Park
2020-01-20 16:27 ` [PATCH 1/8] mm: " SeongJae Park
2020-01-20 16:27 ` [PATCH 2/8] mm/damon: Implement region based sampling SeongJae Park
2020-01-22 8:15 ` SeongJae Park
2020-01-22 8:15 ` SeongJae Park
2020-01-20 16:27 ` [PATCH 3/8] mm/damon: Adaptively adjust regions SeongJae Park
2020-01-20 16:27 ` [PATCH 4/8] mm/damon: Apply dynamic memory mapping changes SeongJae Park
2020-01-20 16:30 ` [PATCH 5/8] mm/damon: Add debugfs interface SeongJae Park
2020-01-20 16:30 ` [PATCH 6/8] mm/damon: Add minimal user-space tools SeongJae Park
2020-01-20 16:30 ` [PATCH 7/8] Documentation/admin-guide/mm: Add a document for DAMON SeongJae Park
2020-01-20 16:30 ` [PATCH 8/8] mm/damon: Add kunit tests SeongJae Park
2020-01-20 16:55 ` Kirill A. Shutemov [this message]
2020-01-20 18:14 ` Re: [PATCH 0/8] Introduce Data Access MONitor (DAMON) SeongJae Park
2020-01-27 16:53 ` sjpark
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=20200120165551.codmosqc2pkcunpa@box \
--to=kirill@shutemov.name \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=amit@kernel.org \
--cc=brendan.d.gregg@gmail.com \
--cc=corbet@lwn.net \
--cc=dwmw@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=rostedt@goodmis.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.