linux-kernel - Re: [PATCH v2 0/9] Introduce Data Access MONitor (DAMON)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <41BBD985-4B3D-4F87-B69D-D8CFE6EC0EBE@lca.pw>
Date:   Tue, 28 Jan 2020 06:20:29 -0500
From:   Qian Cai <cai@....pw>
To:     sjpark@...zon.com
Cc:     akpm@...ux-foundation.org, SeongJae Park <sjpark@...zon.de>,
        sj38.park@...il.com, acme@...nel.org, amit@...nel.org,
        brendan.d.gregg@...il.com, corbet@....net, dwmw@...zon.com,
        mgorman@...e.de, rostedt@...dmis.org, kirill@...temov.name,
        brendanhiggins@...gle.com, colin.king@...onical.com,
        minchan@...nel.org, vdavydov.dev@...il.com, vdavydov@...allels.com,
        linux-mm@...ck.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/9] Introduce Data Access MONitor (DAMON)



> On Jan 28, 2020, at 5:50 AM, sjpark@...zon.com wrote:
> 
> 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.
> 
> 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 described
> below in the original cover letter.
> 
> 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 frames
> while DAMON deals with virtual address of specific processes.
> 
> Nevertheless, if you have some different opinion, please let me know.

I thought everyone should know to go to the MAINTAINERS file and search PERFORMANCE EVENTS SUBSYSTEM.

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