Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From:   Qian Cai <cai@lca.pw>
Mime-Version: 1.0 (1.0)
Subject: Re: [PATCH v2 0/9] Introduce Data Access MONitor (DAMON)
Date:   Tue, 28 Jan 2020 06:20:29 -0500
Message-Id: <41BBD985-4B3D-4F87-B69D-D8CFE6EC0EBE@lca.pw>
References: <20200128104942.11419-1-sjpark@amazon.com>
Cc:     akpm@linux-foundation.org, SeongJae Park <sjpark@amazon.de>,
        sj38.park@gmail.com, 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, vdavydov@parallels.com,
        linux-mm@kvack.org, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org
In-Reply-To: <20200128104942.11419-1-sjpark@amazon.com>
To:     sjpark@amazon.com
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Jan 28, 2020, at 5:50 AM, sjpark@amazon.com wrote:
>=20
> For the comments from perf maintainers, I added Steven Rostedt and Arnaldo=

> Carvalho de Melo first, but I might missed someone.  If you recommend some=
 more
> people, I will add them to recipients.
>=20
> I made DAMON as a new subsystem because I think no existing subsystem fits=
 well
> to be a base of DAMON, due to DAMON's unique goals and mechanisms describe=
d
> below in the original cover letter.
>=20
> The existing subsystem that most similar to DAMON might be 'mm/page_idle.c=
'.
> However, there are many conceptual differences with DAMON.  One biggest
> difference I think is the target.  'page_idle' deals with physical page fr=
ames
> while DAMON deals with virtual address of specific processes.
>=20
> Nevertheless, if you have some different opinion, please let me know.

I thought everyone should know to go to the MAINTAINERS file and search PERFO=
RMANCE EVENTS SUBSYSTEM.

It might be difficult but there is a perf subcommand for some subsystems lik=
e sched: tracing/measuring of scheduler actions and latencies.=