linux-kernel - Re: [PATCH] mm: Move readahead limit outside of readahead, and advisory syscalls

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]

Date:   Thu, 25 Aug 2016 10:59:45 -0400
From:   Kyle Walker <kwalker@...hat.com>
To:     Rafael Aquini <aquini@...hat.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
        lkml <linux-kernel@...r.kernel.org>,
        Michal Hocko <mhocko@...e.com>,
        Geliang Tang <geliangtang@....com>,
        Vlastimil Babka <vbabka@...e.cz>,
        Roman Gushchin <klamm@...dex-team.ru>,
        "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] mm: Move readahead limit outside of readahead, and
 advisory syscalls

On Wed, Aug 3, 2016 at 11:24 AM, Rafael Aquini <aquini@...hat.com> wrote:
> IIRC one of the issues Linus had with previous attempts was because
> they were utilizing/bringing back a node-memory state based heuristic.
>
> Since Kyle patch is using a global state counter for that matter,
> I think that issue condition might now be sorted out.

It's been a few weeks since the last feedback. Are there any further
questions or concerns I can help out with?

--
Kyle Walker