From: "Du, Changbin" <changbin.du@intel.com>
To: "Михаил Гаврилов" <mikhail.v.gavrilov@gmail.com>
Cc: "Du, Changbin" <changbin.du@intel.com>, linux-mm@kvack.org
Subject: Re: swapper/0: page allocation failure: order:0, mode:0x1204010(GFP_NOWAIT|__GFP_COMP|__GFP_RECLAIMABLE|__GFP_NOTRACK), nodemask=(null)
Date: Fri, 20 Oct 2017 14:43:06 +0800 [thread overview]
Message-ID: <20171020064305.GA13688@intel.com> (raw)
In-Reply-To: <CABXGCsPL0pUHo_M-KxB3mabfdGMSHPC0uchLBBt0JCzF2BYBww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
On Thu, Oct 19, 2017 at 11:52:49PM +0500, Михаил Гаврилов wrote:
> On 19 October 2017 at 08:56, Du, Changbin <changbin.du@intel.com> wrote:
> > On Thu, Oct 19, 2017 at 01:16:48AM +0500, Михаил Гаврилов wrote:
> > I am curious about this, how can slub try to alloc compound page but the order
> > is 0? This is wrong.
>
> Nobody seems to know how this could happen. Can any logs shed light on this?
>
After checking the code, kernel can handle such case. So please ignore my last
comment.
The warning is reporting OOM, first you need confirm if you have enough free
memory? If that is true, then it is not a programmer error.
> --
> Best Regards,
> Mike Gavrilov.
--
Thanks,
Changbin Du
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-10-20 6:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 20:16 swapper/0: page allocation failure: order:0, mode:0x1204010(GFP_NOWAIT|__GFP_COMP|__GFP_RECLAIMABLE|__GFP_NOTRACK), nodemask=(null) Михаил Гаврилов
2017-10-19 3:56 ` Du, Changbin
2017-10-19 18:52 ` Михаил Гаврилов
2017-10-20 6:43 ` Du, Changbin [this message]
2017-10-20 9:12 ` Michal Hocko
2017-10-24 19:30 ` Михаил Гаврилов
2017-10-24 20:06 ` Michal Hocko
2017-10-26 17:49 ` Михаил Гаврилов
2017-10-29 21:48 ` Михаил Гаврилов
2017-11-02 13:15 ` Tetsuo Handa
2017-11-02 15:01 ` Michal Hocko
2017-11-02 15:06 ` Michal Hocko
2017-11-06 20:48 ` Михаил Гаврилов
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=20171020064305.GA13688@intel.com \
--to=changbin.du@intel.com \
--cc=linux-mm@kvack.org \
--cc=mikhail.v.gavrilov@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;
as well as URLs for NNTP newsgroup(s).