From: Matthew Wilcox <willy@infradead.org>
To: Pekka Enberg <penberg@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Dan Williams <dan.j.williams@intel.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: 5.8.0rc3 page allocation failure: order:0, mode:0x40810
Date: Sat, 4 Jul 2020 13:01:35 +0100 [thread overview]
Message-ID: <20200704120135.GO25523@casper.infradead.org> (raw)
In-Reply-To: <CAOJsxLEi=TQGrQm+ksdaZUE8TQijJ-66dxZ_DNR3xkoM9xDbAQ@mail.gmail.com>
On Sat, Jul 04, 2020 at 02:49:32PM +0300, Pekka Enberg wrote:
> Hi Matthew,
>
> On Sat, Jul 4, 2020 at 2:37 PM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > On Sat, Jul 04, 2020 at 01:21:05AM -0600, Chris Murphy wrote:
> > > Hi,
> > >
> > > This seems to be a one off - I'm not even sure what was happening at
> > > the time. Possibly running a qemu-kvm VM.
> > >
> > > 5.8.0-0.rc3.1.fc33.x86_64+debug
> > > i7-2820QM
> > > MemTotal: 8021304 kB
> > > $ swapon
> > > NAME TYPE SIZE USED PRIO
> > > /dev/sda5 partition 10.4G 0B -2
> > > /dev/zram0 partition 3.8G 9M 100
> > > $ zramctl
> > > NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
> > > /dev/zram0 lzo-rle 3.8G 7.8M 2.3M 4.5M 8 [SWAP]
> > >
> > >
> > >
> > >
> > > [126841.385050] swapper/2: page allocation failure: order:0,
> > > mode:0x40810(GFP_NOWAIT|__GFP_COMP|__GFP_RECLAIMABLE),
> >
> > This is one for Dan; he decided to use GFP_NOWAIT in commit
> > 0abdd7a81b7e3fd781d7fabcca49501852bba17e
>
> Why is that a problem? Unless I am missing something, there's plenty
> of free pages available for the slab allocation:
>
> > > [126841.385277] Node 0 Normal: 366*4kB (UME) 413*8kB (UME) 76*16kB
> > > (UME) 18*32kB (UME) 20*64kB (UME) 16*128kB (UME) 10*256kB (UME)
> > > 8*512kB (ME) 5*1024kB (UE) 2*2048kB (UM) 6*4096kB (M) = 50336kB
One of the things we (mostly Mike Kravetz) found recently when debugging
a memory allocation stall issue is that this message does not capture
the state which actually caused the message to be printed. In the
intervening time between the memory allocation failure being detected
and this message being printed, kswapd may have made forward progress.
next prev parent reply other threads:[~2020-07-04 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 7:21 Chris Murphy
2020-07-04 8:02 ` Pekka Enberg
2020-07-04 11:37 ` Matthew Wilcox
2020-07-04 11:49 ` Pekka Enberg
2020-07-04 12:01 ` Matthew Wilcox [this message]
2020-07-04 18:33 ` Pekka Enberg
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=20200704120135.GO25523@casper.infradead.org \
--to=willy@infradead.org \
--cc=dan.j.williams@intel.com \
--cc=linux-mm@kvack.org \
--cc=lists@colorremedies.com \
--cc=mike.kravetz@oracle.com \
--cc=penberg@gmail.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