From: SeongJae Park <sjpark@amazon.com>
To: SeongJae Park <sjpark@amazon.com>
Cc: <akpm@linux-foundation.org>, SeongJae Park <sjpark@amazon.de>,
<Jonathan.Cameron@Huawei.com>, <aarcange@redhat.com>,
<acme@kernel.org>, <alexander.shishkin@linux.intel.com>,
<amit@kernel.org>, <benh@kernel.crashing.org>,
<brendan.d.gregg@gmail.com>, <brendanhiggins@google.com>,
<cai@lca.pw>, <colin.king@canonical.com>, <corbet@lwn.net>,
<dwmw@amazon.com>, <foersleo@amazon.de>, <irogers@google.com>,
<jolsa@redhat.com>, <kirill@shutemov.name>,
<mark.rutland@arm.com>, <mgorman@suse.de>, <minchan@kernel.org>,
<mingo@redhat.com>, <namhyung@kernel.org>, <peterz@infradead.org>,
<rdunlap@infradead.org>, <riel@surriel.com>,
<rientjes@google.com>, <rostedt@goodmis.org>, <sblbir@amazon.com>,
<shakeelb@google.com>, <shuah@kernel.org>, <sj38.park@gmail.com>,
<snu@amazon.de>, <vbabka@suse.cz>, <vdavydov.dev@gmail.com>,
<yang.shi@linux.alibaba.com>, <ying.huang@intel.com>,
<david@redhat.com>, <linux-damon@amazon.com>,
<linux-mm@kvack.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC v4 0/8] DAMON: Support Access Monitoring of Any Address Space Including Physical Memory
Date: Tue, 16 Jun 2020 16:34:33 +0200 [thread overview]
Message-ID: <20200616143433.23710-1-sjpark@amazon.com> (raw)
In-Reply-To: <20200616140813.17863-1-sjpark@amazon.com> (raw)
Sorry, the cover letter for previous version of the patchset was mistakenly
sent. Below is the proper coverletter for this version.
================================ >8 ===========================================
Subject: [RFC v4 0/8] DAMON: Support Physical Memory Address Space Monitoring
DAMON[1] programming interface users can extend DAMON for any address space by
implementing and using their own address-space specific low level primitives.
However, the user space users who rely on the debugfs interface and user space
tool, can monitor the virtual address space only. This is mainly due to DAMON
is providing the reference implementation of the low level primitives for the
virtual address space only.
This patchset implements another reference implementation of the low level
primitives for the physical memory address space. Therefore, users can monitor
both of the virtual and the physical address spaces by simply configuring the
provided low level primitives. Further, this patchset links the
implementation to the debugfs interface and the user space tool, so that user
space users can also use the features.
Note that the implementation supports only the user memory, as same to the idle
page access tracking feature.
[1] https://lore.kernel.org/linux-mm/20200615161927.12637-1-sjpark@amazon.com/
Baseline and Complete Git Trees
===============================
The patches are based on the v5.7 plus DAMON v16 patchset[1] and DAMOS RFC v12
patchset[2]. You can also clone the complete git tree:
$ git clone git://github.com/sjp38/linux -b cdamon/rfc/v4
The web is also available:
https://github.com/sjp38/linux/releases/tag/cdamon/rfc/v4
[1] https://lore.kernel.org/linux-mm/20200615161927.12637-1-sjpark@amazon.com/
[2] https://lore.kernel.org/linux-mm/20200616073828.16509-1-sjpark@amazon.com/
Sequence of Patches
===================
The sequence of patches is as follow.
The 1st and 2nd patches allow the debugfs interface and the user space tool to
be able to set the monitoring target regions as they want, respectively. The
3rd patch documents the feature.
The 4th patch exports rmap essential functions to GPL modules as those are
required from the DAMON's reference implementation of the low level primitives
for the physical memory address space. The 5th patch provides the reference
implementations of the configurable primitives for the physical memory
monitoring. The 6th and 7th patches make the user space to be able to use the
physical memory monitoring via debugfs and the user space tool, respectively.
Finally, the 8th patch documents the physical memory monitoring support.
Patch History
=============
Changes from RFC v3
(https://lore.kernel.org/linux-mm/20200609141941.19184-1-sjpark@amazon.com/)
- Export rmap functions
- Reorganize for physical memory monitoring support only
- Clean up debugfs code
Changes from RFC v2
(https://lore.kernel.org/linux-mm/20200603141135.10575-1-sjpark@amazon.com/)
- Support the physical memory monitoring with the user space tool
- Use 'pfn_to_online_page()' (David Hildenbrand)
- Document more detail on random 'pfn' and its safeness (David Hildenbrand)
Changes from RFC v1
(https://lore.kernel.org/linux-mm/20200409094232.29680-1-sjpark@amazon.com/)
- Provide the reference primitive implementations for the physical memory
- Connect the extensions with the debugfs interface
SeongJae Park (8):
mm/damon/debugfs: Allow users to set initial monitoring target regions
tools/damon: Implement init target regions feature
Docs/damon: Document 'initial_regions' feature
mm/rmap: Export essential functions for rmap_run
mm/damon: Implement callbacks for physical memory monitoring
mm/damon/debugfs: Support physical memory monitoring
tools/damon/record: Support physical memory address spce
Docs/damon: Document physical memory monitoring support
Documentation/admin-guide/mm/damon/faq.rst | 7 +-
Documentation/admin-guide/mm/damon/index.rst | 1 -
Documentation/admin-guide/mm/damon/plans.rst | 7 -
Documentation/admin-guide/mm/damon/usage.rst | 73 +++-
include/linux/damon.h | 5 +
mm/damon.c | 374 ++++++++++++++++++-
mm/rmap.c | 2 +
mm/util.c | 1 +
tools/damon/_damon.py | 41 ++
tools/damon/heats.py | 2 +-
tools/damon/record.py | 41 +-
tools/damon/schemes.py | 12 +-
12 files changed, 532 insertions(+), 34 deletions(-)
delete mode 100644 Documentation/admin-guide/mm/damon/plans.rst
--
2.17.1
prev parent reply other threads:[~2020-06-16 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 14:08 [RFC v4 0/8] DAMON: Support Access Monitoring of Any Address Space Including Physical Memory SeongJae Park
2020-06-16 14:08 ` [RFC v4 1/8] mm/damon/debugfs: Allow users to set initial monitoring target regions SeongJae Park
2020-06-16 14:08 ` [RFC v4 2/8] tools/damon: Implement init target regions feature SeongJae Park
2020-06-16 14:08 ` [RFC v4 3/8] Docs/damon: Document 'initial_regions' feature SeongJae Park
2020-06-16 14:08 ` [RFC v4 4/8] mm/rmap: Export essential functions for rmap_run SeongJae Park
2020-06-16 14:08 ` [RFC v4 5/8] mm/damon: Implement callbacks for physical memory monitoring SeongJae Park
2020-06-16 14:08 ` [RFC v4 6/8] mm/damon/debugfs: Support " SeongJae Park
2020-06-16 14:08 ` [RFC v4 7/8] tools/damon/record: Support physical memory address spce SeongJae Park
2020-06-16 14:08 ` [RFC v4 8/8] Docs/damon: Document physical memory monitoring support SeongJae Park
2020-06-16 14:34 ` 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=20200616143433.23710-1-sjpark@amazon.com \
--to=sjpark@amazon.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=aarcange@redhat.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=brendan.d.gregg@gmail.com \
--cc=brendanhiggins@google.com \
--cc=cai@lca.pw \
--cc=colin.king@canonical.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dwmw@amazon.com \
--cc=foersleo@amazon.de \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kirill@shutemov.name \
--cc=linux-damon@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=sblbir@amazon.com \
--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=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.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).