From: SeongJae Park <sj38.park@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: SeongJae Park <sj38.park@gmail.com>,
sjpark@amazon.com, akpm@linux-foundation.org,
SeongJae Park <sjpark@amazon.de>,
acme@kernel.org, amit@kernel.org, brendan.d.gregg@gmail.com,
corbet@lwn.net, dwmw@amazon.com, mgorman@suse.de,
rostedt@goodmis.org, kirill@shutemov.name,
brendanhiggins@google.com, colin.king@canonical.com,
minchan@kernel.org, vdavydov.dev@gmail.com, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: Re: Re: Re: Re: [PATCH v2 0/9] Introduce Data Access MONitor (DAMON)
Date: Wed, 29 Jan 2020 20:59:07 +0100 [thread overview]
Message-ID: <20200129195907.4589-1-sj38.park@gmail.com> (raw)
In-Reply-To: <20200129193616.GT14914@hirez.programming.kicks-ass.net> (raw)
On Wed, 29 Jan 2020 20:36:16 +0100 Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Jan 29, 2020 at 08:06:45PM +0100, SeongJae Park wrote:
> > > Perf can do address based sampling of memops, I suspect you can create
> > > something using that.
> >
> > If you're saying implementing DAMON in 'perf mem', I think it would conflict
> > with abovely explained DAMON's goal.
> >
> > Else, if you're saying it would be the right place to handle the DAMON
> > generated data, I agree, thank you for pointing me that. Will keep it in mind
> > while shaping the interface of DAMON.
>
> I'm saying it might be able to provide the data you need; without damon.
>
> Might; because I'm not entirely sure what you're looking for, nor
> exactly what events we have that provide address information.
Thank you for further clarifying this :) Will also address this concern in
next spin.
Thanks,
SeongJae Park
prev parent reply other threads:[~2020-01-29 19:59 UTC|newest]
Thread overview: 33+ 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-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 0:02 ` Brendan Higgins
2020-01-31 4:44 ` SeongJae Park
2020-02-01 8:52 ` SeongJae Park
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 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-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 [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=20200129195907.4589-1-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--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=jolsa@redhat.com \
--cc=kirill@shutemov.name \
--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=rostedt@goodmis.org \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.de \
--cc=vdavydov.dev@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.