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

[Kyle Walker]

On Wed, Aug 3, 2016 at 11:24 AM, Rafael Aquini <aquini@xxxxxxxxxx> 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