From: Davidlohr Bueso <dave@stgolabs.net>
To: Gregory Price <gourry@gourry.net>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-team@meta.com, akpm@linux-foundation.org,
ying.huang@intel.com, weixugc@google.com,
dave.hansen@linux.intel.com, osalvador@suse.de,
shy828301@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH] vmscan,migrate: fix double-decrement on node stats when demoting pages
Date: Mon, 28 Oct 2024 09:05:43 -0700 [thread overview]
Message-ID: <20241028160543.rzx6nqsyldwocxe6@offworld> (raw)
In-Reply-To: <20241025141724.17927-1-gourry@gourry.net>
On Fri, 25 Oct 2024, Gregory Price wrote:
>When numa balancing is enabled with demotion, vmscan will call
>migrate_pages when shrinking LRUs. Successful demotions will
>cause node vmstat numbers to double-decrement, leading to an
>imbalanced page count. The result is dmesg output like such:
>
>$ cat /proc/sys/vm/stat_refresh
>
>[77383.088417] vmstat_refresh: nr_isolated_anon -103212
>[77383.088417] vmstat_refresh: nr_isolated_file -899642
>
>This negative value may impact compaction and reclaim throttling.
>
>The double-decrement occurs in the migrate_pages path:
>
>caller to shrink_folio_list decrements the count
> shrink_folio_list
> demote_folio_list
> migrate_pages
> migrate_pages_batch
> migrate_folio_move
> migrate_folio_done
> mod_node_page_state(-ve) <- second decrement
>
>This path happens for SUCCESSFUL migrations, not failures. Typically
>callers to migrate_pages are required to handle putback/accounting for
>failures, but this is already handled in the shrink code.
>
>When accounting for migrations, instead do not decrement the count
>when the migration reason is MR_DEMOTION. As of v6.11, this demotion
>logic is the only source of MR_DEMOTION.
>
>Signed-off-by: Gregory Price <gourry@gourry.net>
>Fixes: 26aa2d199d6f2 ("mm/migrate: demote pages during reclaim")
>Cc: stable@vger.kernel.org
Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>
next prev parent reply other threads:[~2024-10-28 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 14:17 Gregory Price
2024-10-28 4:39 ` Huang, Ying
2024-10-28 5:24 ` Shakeel Butt
2024-10-28 14:39 ` Gregory Price
2024-10-29 0:16 ` Huang, Ying
2024-10-28 16:05 ` Davidlohr Bueso [this message]
2024-10-28 20:45 ` Yang Shi
2024-10-28 21:25 ` Gregory Price
2024-10-29 0:34 ` Huang, Ying
2024-10-29 13:14 ` Gregory Price
2024-10-29 8:40 ` Oscar Salvador
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=20241028160543.rzx6nqsyldwocxe6@offworld \
--to=dave@stgolabs.net \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=gourry@gourry.net \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=stable@vger.kernel.org \
--cc=weixugc@google.com \
--cc=ying.huang@intel.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