From: Matthew Wilcox <willy@infradead.org>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmscan: don't try to reclaim freed folios
Date: Fri, 27 May 2022 16:02:25 +0100 [thread overview]
Message-ID: <YpDoAZtQtQf6U8D2@casper.infradead.org> (raw)
In-Reply-To: <20220527080451.48549-1-linmiaohe@huawei.com>
On Fri, May 27, 2022 at 04:04:51PM +0800, Miaohe Lin wrote:
> If folios were freed from under us, there's no need to reclaim them. Skip
> these folios to save lots of cpu cycles and avoid possible unnecessary
> disk IO.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> mm/vmscan.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index f7d9a683e3a7..646dd1efad32 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -1556,12 +1556,18 @@ static unsigned int shrink_page_list(struct list_head *page_list,
> folio = lru_to_folio(page_list);
> list_del(&folio->lru);
>
> + nr_pages = folio_nr_pages(folio);
> + if (folio_ref_count(folio) == 1) {
> + /* folio was freed from under us. So we are done. */
> + WARN_ON(!folio_put_testzero(folio));
What? No. This can absolutely happen. We have a refcount on the folio,
which means that any other thread can temporarily raise the refcount,
so this WARN_ON can trigger. Also, we don't hold the folio locked,
or an extra reference, so nr_pages is unstable because it can be split.
> + goto free_it;
> + }
> +
> if (!folio_trylock(folio))
> goto keep;
>
> VM_BUG_ON_FOLIO(folio_test_active(folio), folio);
>
> - nr_pages = folio_nr_pages(folio);
>
> /* Account the number of base pages */
> sc->nr_scanned += nr_pages;
> --
> 2.23.0
>
>
next prev parent reply other threads:[~2022-05-27 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 8:04 Miaohe Lin
2022-05-27 15:02 ` Matthew Wilcox [this message]
2022-05-28 2:52 ` Miaohe Lin
2022-05-28 3:13 ` Matthew Wilcox
2022-05-28 6:24 ` Miaohe Lin
2022-06-08 14:09 ` Miaohe Lin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YpDoAZtQtQf6U8D2@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox