From: Baoquan He <baoquan.he@linux.dev>
To: "Barry Song (Xiaomi)" <baohua@kernel.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org, chrisl@kernel.org,
david@kernel.org, jp.kobryn@linux.dev, kasong@tencent.com,
liam@infradead.org, linux-kernel@vger.kernel.org, ljs@kernel.org,
mhocko@suse.com, nphamcs@gmail.com, rppt@kernel.org,
shakeel.butt@linux.dev, shikemeng@huaweicloud.com,
surenb@google.com, usama.arif@linux.dev, vbabka@kernel.org,
youngjun.park@lge.com
Subject: Re: [PATCH v3 1/4] mm: avoid unnecessary lru drain for wp_can_reuse_anon_folio()
Date: Tue, 7 Jul 2026 20:55:18 +0800 [thread overview]
Message-ID: <akz3NnXR2uP9ID2E@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20260701235955.36126-2-baohua@kernel.org>
On 07/02/26 at 07:59am, Barry Song (Xiaomi) wrote:
> There is a case where `folio_ref_count(folio) == 3` and
> `!folio_test_swapcache(folio)`. In that case, both
> `folio_ref_count(folio) > 3` and
> `folio_ref_count(folio) > 1 + folio_test_swapcache(folio)` evaluate
> false, causing an unnecessary local LRU drain.
>
> During an Ubuntu boot, I observed over 5,000 redundant local LRU
> drains. For a kernel build with a minimal configuration, I observed
> more than 20,000 redundant drains.
>
> Fix this by checking against: `1 + in_swapcache + in_lrucache`
> instead of hardcoding `folio_ref_count(folio) > 3`.
>
> Suggested-by: David Hildenbrand (Arm) <david@kernel.org>
> Reviewed-by: Kairui Song <kasong@tencent.com>
> Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
> Reviewed-by: Baoquan He <baoquan.he@linux.dev>
> Signed-off-by: Barry Song (Xiaomi) <baohua@kernel.org>
> ---
> mm/memory.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
Rechecked, LGTM,
Reviewed-by: Baoquan He <baoquan.he@linux.dev>
>
> diff --git a/mm/memory.c b/mm/memory.c
> index ff338c2abe92..87da78eb1abd 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -4181,6 +4181,9 @@ static bool __wp_can_reuse_large_anon_folio(struct folio *folio,
> static bool wp_can_reuse_anon_folio(struct folio *folio,
> struct vm_area_struct *vma)
> {
> + const bool in_lru_cache = !folio_test_lru(folio);
> + const bool in_swapcache = folio_test_swapcache(folio);
> +
> if (IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE) && folio_test_large(folio))
> return __wp_can_reuse_large_anon_folio(folio, vma);
>
> @@ -4191,15 +4194,16 @@ static bool wp_can_reuse_anon_folio(struct folio *folio,
> *
> * KSM doesn't necessarily raise the folio refcount.
> */
> - if (folio_test_ksm(folio) || folio_ref_count(folio) > 3)
> + if (folio_test_ksm(folio) ||
> + folio_ref_count(folio) > 1 + in_lru_cache + in_swapcache)
> return false;
> - if (!folio_test_lru(folio))
> + if (in_lru_cache)
> /*
> * We cannot easily detect+handle references from
> * remote LRU caches or references to LRU folios.
> */
> lru_add_drain();
> - if (folio_ref_count(folio) > 1 + folio_test_swapcache(folio))
> + if (folio_ref_count(folio) > 1 + in_swapcache)
> return false;
> if (!folio_trylock(folio))
> return false;
> --
> 2.39.3 (Apple Git-146)
>
prev parent reply other threads:[~2026-07-07 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260701235955.36126-1-baohua@kernel.org>
[not found] ` <20260701235955.36126-3-baohua@kernel.org>
[not found] ` <3a185a5d-2f2c-4e9d-9cd9-8bdb236dfc5c@kernel.org>
2026-07-06 8:14 ` [PATCH v3 2/4] mm: drop stale folio_ref_count()==1 check in do_swap_page reuse logic Barry Song
2026-07-07 11:08 ` Barry Song
[not found] ` <20260701235955.36126-2-baohua@kernel.org>
[not found] ` <a9829fdd-75b3-4035-935a-f3a74fdc29bc@kernel.org>
2026-07-06 8:18 ` [PATCH v3 1/4] mm: avoid unnecessary lru drain for wp_can_reuse_anon_folio() Barry Song
2026-07-06 9:12 ` Baoquan He
2026-07-06 9:17 ` Barry Song
2026-07-07 12:55 ` Baoquan He [this message]
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=akz3NnXR2uP9ID2E@MiWiFi-R3L-srv \
--to=baoquan.he@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=jp.kobryn@linux.dev \
--cc=kasong@tencent.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=nphamcs@gmail.com \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=youngjun.park@lge.com \
/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