linux-kernel - Re: Re: [PATCH v9 00/15] 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] [day] [month] [year] [list]

Message-ID: <20200429101019.26299-1-sjpark@amazon.com>
Date:   Wed, 29 Apr 2020 12:10:19 +0200
From:   SeongJae Park <sjpark@...zon.com>
To:     Jonathan Cameron <Jonathan.Cameron@...wei.com>
CC:     SeongJae Park <sjpark@...zon.com>, <akpm@...ux-foundation.org>,
        "SeongJae Park" <sjpark@...zon.de>, <aarcange@...hat.com>,
        <acme@...nel.org>, <alexander.shishkin@...ux.intel.com>,
        <amit@...nel.org>, <benh@...nel.crashing.org>,
        <brendan.d.gregg@...il.com>, <brendanhiggins@...gle.com>,
        <cai@....pw>, <colin.king@...onical.com>, <corbet@....net>,
        <dwmw@...zon.com>, <irogers@...gle.com>, <jolsa@...hat.com>,
        <kirill@...temov.name>, <mark.rutland@....com>, <mgorman@...e.de>,
        <minchan@...nel.org>, <mingo@...hat.com>, <namhyung@...nel.org>,
        <peterz@...radead.org>, <rdunlap@...radead.org>,
        <riel@...riel.com>, <rientjes@...gle.com>, <rostedt@...dmis.org>,
        <sblbir@...zon.com>, <shakeelb@...gle.com>, <shuah@...nel.org>,
        <sj38.park@...il.com>, <snu@...zon.de>, <vbabka@...e.cz>,
        <vdavydov.dev@...il.com>, <yang.shi@...ux.alibaba.com>,
        <ying.huang@...el.com>, <linux-damon@...zon.com>,
        <linux-mm@...ck.org>, <linux-doc@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: Re: [PATCH v9 00/15] Introduce Data Access MONitor (DAMON)

On Wed, 29 Apr 2020 10:18:06 +0100 Jonathan Cameron <Jonathan.Cameron@...wei.com> wrote:

> On Wed, 29 Apr 2020 09:49:54 +0200
> SeongJae Park <sjpark@...zon.com> wrote:
> 
> > On Tue, 28 Apr 2020 17:17:13 +0100 Jonathan Cameron <Jonathan.Cameron@...wei.com> wrote:
> > 
> > > On Tue, 28 Apr 2020 15:23:42 +0200
> > > SeongJae Park <sjpark@...zon.com> wrote:
> > >   
> > > > On Tue, 28 Apr 2020 13:27:04 +0100 Jonathan Cameron <Jonathan.Cameron@...wei.com> wrote:
> > > >   
> > > > > On Mon, 27 Apr 2020 14:04:27 +0200
> > > > > SeongJae Park <sjpark@...zon.com> wrote:
> > > > >     
> > > > > > From: SeongJae Park <sjpark@...zon.de>
> > > > > > 
> > > > > > Introduction
> > > > > > ============
> > > > > > 
[...]
> > 
> > Appreciate your explanations and suggestions.
> 
> You are welcome.
> 
> Out of interest, do you have any comparative data on how 'accurate' the resulting
> estimates are vs a more precise heatmap from a memory trace?

No, I don't have such data.

I'm only comparing the big trends of heatmap, working set sizes analyzed from
the recorded access pattern and the DAMOS performance results for each version
using my human eye, to check regression.

> 
> I'm looking at gathering such data but much happier to leverage your work if
> you've already done it!

That would be great.  If I get such data later, I will let you know.  I will be
also very happy if you could get it first and share with me.

Maybe we could make and use another variant of DAMON, which uses page-size
regions only and disable the adaptive regions adjustment.  It will be also
useful for overhead comparison.  Actually, I heard that my previous colleague
made this variant for the comparison based on a prototype of DAMON.  I will
also consider extending DAMON to support such variant.

Also, if you need the heatmaps, analyzed working set size distribution, and/or
the record file itself for each version of the patchsets, please let me know.


Thanks,
SeongJae Park