From: SeongJae Park <sj38.park@gmail.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: Brendan Higgins <brendanhiggins@google.com>,
SeongJae Park <sjpark@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
SeongJae Park <sjpark@amazon.de>,
acme@kernel.org, amit@kernel.org, brendan.d.gregg@gmail.com,
Jonathan Corbet <corbet@lwn.net>,
dwmw@amazon.com, mgorman@suse.de,
Steven Rostedt <rostedt@goodmis.org>,
kirill@shutemov.name, colin.king@canonical.com,
minchan@kernel.org, vdavydov.dev@gmail.com,
vdavydov@parallels.com, linux-mm@kvack.org,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Re: Re: [PATCH v2 6/9] mm/damon: Add minimal user-space tools
Date: Sat, 1 Feb 2020 09:52:33 +0100 [thread overview]
Message-ID: <20200201085233.28942-1-sj38.park@gmail.com> (raw)
In-Reply-To: <20200131044427.29930-1-sj38.park@gmail.com> (raw)
On Fri, 31 Jan 2020 05:44:27 +0100 SeongJae Park <sj38.park@gmail.com> wrote:
> On Thu, 30 Jan 2020 16:02:26 -0800 Brendan Higgins <brendanhiggins@google.com> wrote:
>
> > On Tue, Jan 28, 2020 at 1:00 AM <sjpark@amazon.com> wrote:
> > >
> > > From: SeongJae Park <sjpark@amazon.de>
> > >
> > > This commit adds a shallow wrapper python script, ``/tools/damon/damo``
> > > that provides more convenient interface. Note that it is only aimed to
> > > be used for minimal reference of the DAMON's raw interfaces and for
> > > debugging of the DAMON itself. Based on the debugfs interface, you can
> > > create another cool and more convenient user space tools.
> > >
> > > Signed-off-by: SeongJae Park <sjpark@amazon.de>
> > > ---
> > > MAINTAINERS | 1 +
> > > tools/damon/.gitignore | 1 +
> > > tools/damon/_dist.py | 35 ++++
> > > tools/damon/bin2txt.py | 64 +++++++
> > > tools/damon/damo | 37 ++++
> > > tools/damon/heats.py | 358 ++++++++++++++++++++++++++++++++++++++
> > > tools/damon/nr_regions.py | 88 ++++++++++
> > > tools/damon/record.py | 194 +++++++++++++++++++++
> > > tools/damon/report.py | 45 +++++
> > > tools/damon/wss.py | 94 ++++++++++
> > > 10 files changed, 917 insertions(+)
> > > create mode 100644 tools/damon/.gitignore
> > > create mode 100644 tools/damon/_dist.py
> > > create mode 100644 tools/damon/bin2txt.py
> > > create mode 100755 tools/damon/damo
> > > create mode 100644 tools/damon/heats.py
> > > create mode 100644 tools/damon/nr_regions.py
> > > create mode 100644 tools/damon/record.py
> > > create mode 100644 tools/damon/report.py
> > > create mode 100644 tools/damon/wss.py
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 5a4db07cad33..95729c138d34 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -4616,6 +4616,7 @@ M: SeongJae Park <sjpark@amazon.de>
> > > L: linux-mm@kvack.org
> > > S: Maintained
> > > F: mm/damon.c
> > > +F: tools/damon/*
> > >
> > > DAVICOM FAST ETHERNET (DMFE) NETWORK DRIVER
> > > L: netdev@vger.kernel.org
> >
> > Another reason to put the MAINTAINERS update at the end; that way you
> > don't have multiple edits sprinkled around your patchset.
>
> I made this change here due to the warning from 'checkpatch.pl' (WARNING:
> added, moved or deleted file(s), does MAINTAINERS need updating?). But, as it
> is just a warning, I think simply ignore it and and make this change at the end
> of the patchset would not be a problem, anyway. What would you prefer?
I think I was too worrying for just warnings. Will ignore the warnings and
move the MAINTAINERS changes to last patch, as you suggested.
Thanks,
SeongJae Park
>
>
> Thanks,
> SeongJae Park
>
next prev parent reply other threads:[~2020-02-01 8:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 8:57 [PATCH v2 0/9] Introduce Data Access MONitor (DAMON) sjpark
2020-01-28 8:57 ` [PATCH v2 1/9] mm: " sjpark
2020-01-28 16:06 ` Randy Dunlap
2020-01-28 16:09 ` sjpark
2020-01-30 23:58 ` Brendan Higgins
2020-01-31 4:38 ` SeongJae Park
2020-01-28 8:57 ` [PATCH v2 2/9] mm/damon: Implement region based sampling sjpark
2020-01-28 8:57 ` [PATCH v2 3/9] mm/damon: Adaptively adjust regions sjpark
2020-01-28 8:57 ` [PATCH v2 4/9] mm/damon: Apply dynamic memory mapping changes sjpark
2020-01-28 8:59 ` [PATCH v2 5/9] mm/damon: Add debugfs interface sjpark
2020-01-28 9:00 ` [PATCH v2 6/9] mm/damon: Add minimal user-space tools sjpark
2020-01-31 0:02 ` Brendan Higgins
2020-01-31 4:44 ` SeongJae Park
2020-02-01 8:52 ` SeongJae Park [this message]
2020-01-28 9:00 ` [PATCH v2 7/9] Documentation/admin-guide/mm: Add a document for DAMON sjpark
2020-01-28 9:01 ` [PATCH v2 8/9] mm/damon: Add kunit tests sjpark
2020-01-31 0:14 ` Brendan Higgins
2020-01-31 4:55 ` SeongJae Park
2020-01-28 9:01 ` [PATCH v2 9/9] mm/damon: Add a tracepoint for result buffer writing sjpark
2020-01-28 10:20 ` [PATCH v2 0/9] Introduce Data Access MONitor (DAMON) Qian Cai
2020-01-28 10:49 ` sjpark
2020-01-28 11:20 ` Qian Cai
2020-01-28 12:00 ` sjpark
2020-01-29 12:56 ` Peter Zijlstra
2020-01-29 14:37 ` sjpark
2020-01-29 18:07 ` Peter Zijlstra
2020-01-29 19:06 ` SeongJae Park
2020-01-29 19:36 ` Peter Zijlstra
2020-01-29 19:59 ` 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=20200201085233.28942-1-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=amit@kernel.org \
--cc=brendan.d.gregg@gmail.com \
--cc=brendanhiggins@google.com \
--cc=colin.king@canonical.com \
--cc=corbet@lwn.net \
--cc=dwmw@amazon.com \
--cc=kirill@shutemov.name \
--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=rostedt@goodmis.org \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.de \
--cc=vdavydov.dev@gmail.com \
--cc=vdavydov@parallels.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).