linux-kernel - Re: Making direct reclaim fail when thrashing

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: <20180727190122.GA3825@bombadil.infradead.org>
Date:   Fri, 27 Jul 2018 12:01:22 -0700
From:   Matthew Wilcox <willy@...radead.org>
To:     Daniel Drake <drake@...lessm.com>
Cc:     mhocko@...nel.org, hannes@...xchg.org, linux-mm@...ck.org,
        linux@...lessm.com, linux-kernel@...r.kernel.org
Subject: Re: Making direct reclaim fail when thrashing

On Fri, Jul 27, 2018 at 11:21:43AM -0500, Daniel Drake wrote:
> Here I'm experimenting by adding another tag to the page cache radix tree,
> tagging pages that were activated in the refault path.

NAK.  No more tags or you blow up the memory consumption of the radix
tree by 15%.

> And then in get_scan_count I'm checking how many active pages have that
> tag, and also looking at the size of the active and inactive lists.

You'd be better off using a bit in struct page somewhere ...