linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Christoph Lameter (Ampere)" <cl@gentwo.org>
To: Matt Fleming <mfleming@cloudflare.com>
Cc: linux-mm@kvack.org, willy@infradead.org,
	 kernel-team <kernel-team@cloudflare.com>
Subject: Re: order-0 page alloc failures during interrupt context on v6.6.43
Date: Fri, 23 Aug 2024 09:09:06 -0700 (PDT)	[thread overview]
Message-ID: <f085975c-d554-53d6-8281-6c22f0b5f839@gentwo.org> (raw)
In-Reply-To: <CAGis_TWzSu=P7QJmjD58WWiu3zjMTVKSzdOwWE8ORaGytzWJwQ@mail.gmail.com>

On Thu, 22 Aug 2024, Matt Fleming wrote:

> I'm seeing page allocation failures across the Cloudflare fleet,
> typically during the network RX path, when trying to allocate order-0
> pages in interrupt context. The machines appear to be under memory
> pressure because the code that gets interrupted is
> shrink_folio_list(). Below is an example stacktrace.
>
> Does anyone have any pointers on how to dig into this some more? It
> appears as though the machines are not able to reclaim memory fast
> enough when under pressure. Happy to provide more metrics or stats on
> request.

Look at the full kernel log output until the time of the allocation
failure? It looks like there is enough memory in every zone to satify the
allocation request.

Stacktrace looks like memory is pushed out via kswapd and zram to
somewhere and then we get interrupted by incoming network traffic.




  parent reply	other threads:[~2024-08-23 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 20:02 Matt Fleming
2024-08-22 22:07 ` Matt Fleming
2024-08-29 15:48   ` Vlastimil Babka
2024-08-30 15:43     ` Matt Fleming
2024-09-01 19:24       ` Vlastimil Babka
2024-08-23 16:09 ` Christoph Lameter (Ampere) [this message]
2024-08-23 20:25   ` Matt Fleming

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=f085975c-d554-53d6-8281-6c22f0b5f839@gentwo.org \
    --to=cl@gentwo.org \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-mm@kvack.org \
    --cc=mfleming@cloudflare.com \
    --cc=willy@infradead.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