All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj38.park@gmail.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: Dongjoo Seo <dseo3@uci.edu>,
	"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@Huawei.com>,
	acme@kernel.org, akpm@linux-foundation.org,
	alexander.shishkin@linux.intel.com, amit@kernel.org,
	benh@kernel.crashing.org, brendanhiggins@google.com,
	corbet@lwn.net, david@redhat.com, dwmw@amazon.com,
	elver@google.com, fan.du@intel.com, foersleo@amazon.de,
	greg@kroah.com, gthelen@google.com, guoju.fgj@alibaba-inc.com,
	jgowans@amazon.com, joe@perches.com, linux-damon@amazon.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, mgorman@suse.de, mheyne@amazon.de,
	minchan@kernel.org, mingo@redhat.com, namhyung@kernel.org,
	peterz@infradead.org, riel@surriel.com, rientjes@google.com,
	rostedt@goodmis.org, rppt@kernel.org, shakeelb@google.com,
	shuah@kernel.org, sieberf@amazon.com, sjpark@amazon.de,
	snu@zelle79.org, vbabka@suse.cz, vdavydov.dev@gmail.com,
	zgf574564920@gmail.com
Subject: Re: [PATCH v34 00/13] Introduce Data Access MONitor (DAMON)
Date: Mon, 26 Jul 2021 13:32:30 +0000	[thread overview]
Message-ID: <20210726133230.1959-1-sjpark@amazon.de> (raw)
In-Reply-To: <20210723083042.2720-1-sjpark@amazon.de>

From: SeongJae Park <sjpark@amazon.de>

On Fri, 23 Jul 2021 08:30:41 +0000 SeongJae Park <sj38.park@gmail.com> wrote:

> From: SeongJae Park <sjpark@amazon.de>
> 
> Hello Dongjoo,
> 
> 
> On Fri, 23 Jul 2021 16:02:44 +0900 Dongjoo Seo <dseo3@uci.edu> wrote:
> 
> > Hello, I am new user of this amazing tool.
> 
> Thank you!  It's always great to meet a new user!
> 
> > I want to use this tool for Nvidia tx2 board with kernel version 4.9.140.
> > 
> > Do you guys have any timeline or update schedule for different kernel version compatibility?
> 
> I didn't have such a plan until now, but I think I can find a time slot to do
> one-time back porting of current DAMON on 4.9.140.  I think continuous support
> would be not so easy, though.  Nevertheless, if you need that, please feel free
> to let me know.  Once it's done, I will notify you.

Thank you for waiting.  I back-ported this patchset and another one for the
physical address space monitoring[1] on v4.9.140.  The source code is available
at DAMON development tree[2].

BTW, I can also agree to Greg's opinion.  For the reason, I also back-ported
the patches on latest v4.9.y[3].  I'd like to suggest you to try that first if
possible.  I also hope this patchset to be merged in mainline in near future,
so that NVIDIA be attracted by DAMON and thus forward-port their drivers on the
latest mainline version.

Nevertheless, DAMOS[4] and DAMON_RECLAIM[5] patchsets are not back-ported
because those need more works, and you are apparently interested in only the
monitoring part.

Please note that this backport is for only one-time.  In other words, I will
not backport the patches for every future 4.9.y release.  Nevertheless, if you
need another backport, please remember I'm here for you.

Finally, a disclaimer.  I did only minimal test for this, as below:

    $ git clone https://github.com/sjp38/masim; make -C masim/
    $ git clone https://github.com/awslabs/damo
    $ # monitor a virtual address space of a process
    $ sudo ./damo/damo record "./masim/masim ./masim/configs/zigzag.cfg"
    $ ./damo/damo report heats --heatmap stdout
    [...]
    88888888888888888888888888888888888888600000000000000000000000000000000000000000
    88888888888888888888888888888888888888600000000000000000000000000000000000000000
    44444444444444444444444444444444444444444444444444444444444444444444444444444200
    00000000000000000000000000000000000000288888888888888888888888888888888888888400
    00000000000000000000000000000000000000288888888888888888888888888888888888888400
    55555555555555555555555555555555555555422222222222222222222222222222222222222100
    88888888888888888888888888888888888888600000000000000000000000000000000000000000
    88888888888888888888888888888888888888600000000000000000000000000000000000000000
    [...]
    # x-axis: space (140021718388736-140021924798416: 196.848 MiB)
    # y-axis: time (247055083700-317341924740: 1 m 10.287 s)
    # resolution: 80x40 (2.461 MiB and 1.757 s for each character)
    $ # monitor the physcial address space of the system
    $ ./masim/masim ./masim/configs/zigzag.cfg &
    $ sudo ./damo/damo record paddr
    00000000000000000000000000000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000000000000000000000000020
    00000000000000000000000000000000000000000000000000000000000000000000000000000040
    [...]
    # x-axis: space (4294967296-136303345616: 122.942 GiB)
    # y-axis: time (356358198969-430518964169: 1 m 14.161 s)
    # resolution: 80x40 (1.537 GiB and 1.854 s for each character)

Hope you get some fun with these backports.

[1] https://lore.kernel.org/linux-mm/20201216094221.11898-1-sjpark@amazon.com/
[2] https://github.com/sjp38/linux/tree/damon/for-v4.9.140
[3] https://github.com/sjp38/linux/tree/damon/for-v4.9.276
[4] https://lore.kernel.org/linux-mm/20201216084404.23183-1-sjpark@amazon.com/
[5] https://lore.kernel.org/linux-mm/20210720131309.22073-1-sj38.park@gmail.com/


Thanks,
SeongJae Park

[...]

  parent reply	other threads:[~2021-07-26 13:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23  7:02 [PATCH v34 00/13] Introduce Data Access MONitor (DAMON) Dongjoo Seo
2021-07-23  7:08 ` Greg KH
2021-07-23  7:16   ` Dongjoo Seo
2021-07-23  7:30     ` Greg KH
2021-07-23  7:51       ` Dongjoo Seo
2021-07-23  8:30 ` SeongJae Park
2021-07-23  8:40   ` SeongJae Park
2021-07-26 13:32   ` SeongJae Park [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-16  8:14 SeongJae Park
2021-07-27 21:30 ` Shakeel Butt
2021-07-27 21:30   ` Shakeel Butt
2021-07-28  8:36   ` SeongJae Park
2021-08-02  8:24     ` SeongJae Park
2021-08-04  7:41       ` SeongJae Park
2021-08-06  0:03     ` Andrew Morton
2021-08-06 11:48       ` SeongJae Park
2021-08-09 14:07         ` SeongJae Park
2021-08-06  0:43 ` Andrew Morton
2021-08-06 11:48   ` SeongJae Park
2021-08-07 18:28     ` Andrew Morton

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=20210726133230.1959-1-sjpark@amazon.de \
    --to=sj38.park@gmail.com \
    --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=dseo3@uci.edu \
    --cc=dwmw@amazon.com \
    --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=jgowans@amazon.com \
    --cc=joe@perches.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=mheyne@amazon.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=sieberf@amazon.com \
    --cc=sjpark@amazon.de \
    --cc=snu@zelle79.org \
    --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 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.