linux-kernel - Re: Re: Re: [PATCH v6 00/14] 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: <20200312104345.10032-1-sjpark@amazon.com>
Date:   Thu, 12 Mar 2020 11:43:45 +0100
From:   SeongJae Park <sjpark@...zon.com>
To:     SeongJae Park <sjpark@...zon.com>
CC:     Shakeel Butt <shakeelb@...gle.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        SeongJae Park <sjpark@...zon.de>,
        "Andrea Arcangeli" <aarcange@...hat.com>,
        Yang Shi <yang.shi@...ux.alibaba.com>, <acme@...nel.org>,
        <alexander.shishkin@...ux.intel.com>, <amit@...nel.org>,
        <brendan.d.gregg@...il.com>, <brendanhiggins@...gle.com>,
        Qian Cai <cai@....pw>,
        Colin Ian King <colin.king@...onical.com>,
        Jonathan Corbet <corbet@....net>, <dwmw@...zon.com>,
        <jolsa@...hat.com>, "Kirill A. Shutemov" <kirill@...temov.name>,
        <mark.rutland@....com>, Mel Gorman <mgorman@...e.de>,
        Minchan Kim <minchan@...nel.org>,
        Ingo Molnar <mingo@...hat.com>, <namhyung@...nel.org>,
        <peterz@...radead.org>, Randy Dunlap <rdunlap@...radead.org>,
        David Rientjes <rientjes@...gle.com>,
        Steven Rostedt <rostedt@...dmis.org>, <shuah@...nel.org>,
        <sj38.park@...il.com>, "Vlastimil Babka" <vbabka@...e.cz>,
        Vladimir Davydov <vdavydov.dev@...il.com>,
        Linux MM <linux-mm@...ck.org>, <linux-doc@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: Re: Re: [PATCH v6 00/14] Introduce Data Access MONitor (DAMON)

On Thu, 12 Mar 2020 11:07:59 +0100 SeongJae Park <sjpark@...zon.com> wrote:

> On Tue, 10 Mar 2020 10:21:34 -0700 Shakeel Butt <shakeelb@...gle.com> wrote:
> 
> > On Mon, Feb 24, 2020 at 4:31 AM SeongJae Park <sjpark@...zon.com> wrote:
> > >
> > > From: SeongJae Park <sjpark@...zon.de>
> > >
> > > Introduction
> > > ============
> > >
[...]
> > 
> > I do want to question the actual motivation of the design followed by this work.
> > 
> > With the already present Page Idle Tracking feature in the kernel, I
> > can envision that the region sampling and adaptive region adjustments
> > can be done in the user space. Due to sampling, the additional
> > overhead will be very small and configurable.
> > 
> > Additionally the proposed mechanism has inherent assumption of the
> > presence of spatial locality (for virtual memory) in the monitored
> > processes which is very workload dependent.
> > 
> > Given that the the same mechanism can be implemented in the user space
> > within tolerable overhead and is workload dependent, why it should be
> > done in the kernel? What exactly is the advantage of implementing this
> > in kernel?
> 
> First of all, DAMON is not for only user space processes, but also for kernel
> space core mechanisms.  Many of the core mechanisms will be able to use DAMON
> for access pattern based optimizations, with light overhead and reasonable
> accuracy.
> 
> Implementing DAMON in user space is of course possible, but it will be
> inefficient.  Using it from kernel space would make no sense, and it would
> incur unnecessarily frequent kernel-user context switches, which is very
> expensive nowadays.

Forgot mentioning about the spatial locality.  Yes, it is workload dependant,
but still pervasive in many case.  Also, many core mechanisms in kernel such as
read-ahead or LRU are already using some similar assumptions.

If it is so problematic, you could set the maximum number of regions to the
number of pages in the system so that each region monitors each page.


Thanks,
SeongJae Park

> 
> 
> Thanks,
> SeongJae Park
> 
> 
> > 
> > thanks,
> > Shakeel
>