[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200212142435.0b7e938fe8112fa35fcbcc71@linux-foundation.org>
Date: Wed, 12 Feb 2020 14:24:35 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Minchan Kim <minchan@...nel.org>
Cc: Matthew Wilcox <willy@...radead.org>, Jan Kara <jack@...e.cz>,
linux-mm <linux-mm@...ck.org>,
Josef Bacik <josef@...icpanda.com>,
Johannes Weiner <hannes@...xchg.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm: fix long time stall from mm_populate
On Wed, 12 Feb 2020 11:53:22 -0800 Minchan Kim <minchan@...nel.org> wrote:
> > That's definitely wrong. It'll clear PageReclaim and then pretend it did
> > nothing wrong.
> >
> > return !PageWriteback(page) ||
> > test_and_clear_bit(PG_reclaim, &page->flags);
> >
>
> Much better, Thanks for the review, Matthew!
> If there is no objection, I will send two patches to Andrew.
> One is PageReadahead strict, the other is limit retry from mm_populate.
With much more detailed changelogs, please!
This all seems rather screwy. if a page is under writeback then it is
uptodate and we should be able to fault it in immediately.
Powered by blists - more mailing lists