linux-kernel - Re: [PATCH v29 05/13] mm/damon: Implement primitives for the virtual memory address spaces

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]

Date:   Tue, 25 May 2021 17:19:04 +0200
From:   <sieberf@...zon.com>
To:     <sj38.park@...il.com>
CC:     <Jonathan.Cameron@...wei.com>, <acme@...nel.org>,
        <akpm@...ux-foundation.org>, <alexander.shishkin@...ux.intel.com>,
        <amit@...nel.org>, <benh@...nel.crashing.org>,
        <brendanhiggins@...gle.com>, <corbet@....net>, <david@...hat.com>,
        <dwmw@...zon.com>, <elver@...gle.com>, <fan.du@...el.com>,
        <foersleo@...zon.de>, <greg@...ah.com>, <gthelen@...gle.com>,
        <guoju.fgj@...baba-inc.com>, <linux-damon@...zon.com>,
        <linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-mm@...ck.org>, <mgorman@...e.de>, <minchan@...nel.org>,
        <mingo@...hat.com>, <namhyung@...nel.org>, <peterz@...radead.org>,
        <riel@...riel.com>, <rientjes@...gle.com>, <rostedt@...dmis.org>,
        <rppt@...nel.org>, <shakeelb@...gle.com>, <shuah@...nel.org>,
        <sjpark@...zon.de>, <snu@...zon.de>, <vbabka@...e.cz>,
        <vdavydov.dev@...il.com>, <zgf574564920@...il.com>
Subject: Re: [PATCH v29 05/13] mm/damon: Implement primitives for the virtual
 memory address spaces

Hi SeongJae,

Some questions for this patch:

Why do we split the regions in 3 areas (heap, stack, mmaped)? I 
understand we don't want to model the whole virtual address space, but 
why don't we just use whatever is modeled by the VMAs to define the 
regions boundaries?

I am not quite understanding why we both set the page idle and young (in 
damon_ptep_mkold). For WSS computation on our end we have used 
pte_clear_young_notify. Why do we touch the page idle flag at all? What 
flags do the reclaim logic use to track access?

Kind regards,

Fernand