From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>,
Mel Gorman <mgorman@suse.de>, Vlastimil Babka <vbabka@suse.cz>,
Tom Lendacky <thomas.lendacky@amd.com>,
Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Jianxiong Gao <jxgao@google.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] mm: Fix endless reclaim on machines with unaccepted memory.
Date: Wed, 17 Jul 2024 14:55:08 +0300 [thread overview]
Message-ID: <xtcmz6b66wayqxzfio4funmrja7ezgmp3mvudjodt5xfx64rot@s6whj735oimb> (raw)
In-Reply-To: <ZpdwcOv9WiILZNvz@tiehlicka>
On Wed, Jul 17, 2024 at 09:19:12AM +0200, Michal Hocko wrote:
> On Tue 16-07-24 16:00:13, Kirill A. Shutemov wrote:
> > Unaccepted memory is considered unusable free memory, which is not
> > counted as free on the zone watermark check. This causes
> > get_page_from_freelist() to accept more memory to hit the high
> > watermark, but it creates problems in the reclaim path.
> >
> > The reclaim path encounters a failed zone watermark check and attempts
> > to reclaim memory. This is usually successful, but if there is little or
> > no reclaimable memory, it can result in endless reclaim with little to
> > no progress. This can occur early in the boot process, just after start
> > of the init process when the only reclaimable memory is the page cache
> > of the init executable and its libraries.
>
> How does this happen when try_to_accept_memory is the first thing to do
> when wmark check fails in the allocation path?
Good question.
I've lost access to the test setup and cannot check it directly right now.
Reading the code Looks like __alloc_pages_bulk() bypasses
get_page_from_freelist() where we usually accept more pages and goes
directly to __rmqueue_pcplist() -> rmqueue_bulk() -> __rmqueue().
Will look more into it when I have access to the test setup.
> Could you describe what was the initial configuration of the system? How
> much of the unaccepted memory was there to trigger this?
This is large TDX guest VM: 176 vCPUs and ~800GiB of memory.
One thing that I noticed that the problem is only triggered when LRU_GEN
enabled. But I failed to identify why.
The system hang (or have very little progress) shortly after systemd
starts.
> > To address this issue, teach shrink_node() and shrink_zones() to accept
> > memory before attempting to reclaim.
> >
> > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > Reported-by: Jianxiong Gao <jxgao@google.com>
> > Fixes: dcdfdd40fa82 ("mm: Add support for unaccepted memory")
> > Cc: stable@vger.kernel.org # v6.5+
> [...]
> > static void shrink_node(pg_data_t *pgdat, struct scan_control *sc)
> > {
> > unsigned long nr_reclaimed, nr_scanned, nr_node_reclaimed;
> > struct lruvec *target_lruvec;
> > bool reclaimable = false;
> >
> > + /* Try to accept memory before going for reclaim */
> > + if (node_try_to_accept_memory(pgdat, sc)) {
> > + if (!should_continue_reclaim(pgdat, 0, sc))
> > + return;
> > + }
> > +
>
> This would need an exemption from the memcg reclaim.
Hm. Could you elaborate why?
--
Kiryl Shutsemau / Kirill A. Shutemov
next prev parent reply other threads:[~2024-07-17 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240716130013.1997325-1-kirill.shutemov@linux.intel.com>
2024-07-17 7:19 ` Michal Hocko
2024-07-17 11:55 ` Kirill A. Shutemov [this message]
2024-07-17 12:06 ` Michal Hocko
2024-07-22 14:07 ` Kirill A. Shutemov
2024-07-23 7:30 ` Vlastimil Babka
2024-07-23 9:49 ` Kirill A. Shutemov
2024-07-23 11:55 ` Michal Hocko
2024-07-23 13:53 ` Kirill A. Shutemov
2024-07-17 21:00 ` Jianxiong Gao
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=xtcmz6b66wayqxzfio4funmrja7ezgmp3mvudjodt5xfx64rot@s6whj735oimb \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=jxgao@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=vbabka@suse.cz \
/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