linux-kernel - Re: [PATCH v2 0/9] workingset protection/detection on the anonymous LRU list

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: <20200229204000.298de32521885b8af858a50d@linux-foundation.org>
Date:   Sat, 29 Feb 2020 20:40:00 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Joonsoo Kim <js1304@...il.com>
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        Johannes Weiner <hannes@...xchg.org>,
        Michal Hocko <mhocko@...nel.org>,
        Hugh Dickins <hughd@...gle.com>,
        Minchan Kim <minchan@...nel.org>,
        Vlastimil Babka <vbabka@...e.cz>,
        Mel Gorman <mgorman@...hsingularity.net>, kernel-team@....com
Subject: Re: [PATCH v2 0/9] workingset protection/detection on the anonymous
 LRU list

On Thu, 27 Feb 2020 16:48:47 +0900 Joonsoo Kim <js1304@...il.com> wrote:

> Hello, Andrew.
> 
> > > * SOLUTION
> > > Since this is what we want to avoid, this patchset implements workingset
> > > protection. Like as the file LRU list, newly created or swap-in anonymous
> > > page is started on the inactive list. Also, like as the file LRU list,
> > > if enough reference happens, the page will be promoted. This simple
> > > modification changes the above example as following.
> > 
> > One wonders why on earth we weren't doing these things in the first
> > place?
> 
> I don't know. I tried to find the origin of this behaviour and found
> that it's from you 18 years ago. :)
> 
> It mentions that starting pages on the active list boosts throughput on
> stupid swapstormy test but I cannot guess the exact reason of such
> improvement.
> 
> Anyway, Following is the related patch history. Could you remember
> anything about it?
> 

erm, yes, that was a long time ago ;) I guess enough other things have
changed since then to necessitate a revisit!