From: Michal Hocko <mhocko@kernel.org>
To: "Du, Changbin" <changbin.du@intel.com>
Cc: "Михаил Гаврилов" <mikhail.v.gavrilov@gmail.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 11:12:39 +0200 [thread overview]
Message-ID: <20171020091239.cfwapdkx5g7afyp7@dhcp22.suse.cz> (raw)
In-Reply-To: <20171020064305.GA13688@intel.com>
On Fri 20-10-17 14:43:06, Du, Changbin wrote:
> On Thu, Oct 19, 2017 at 11:52:49PM +0500, D?D,N?D?D,D>> D?D?D2N?D,D>>D 3/4 D2 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, D?D,N?D?D,D>> D?D?D2N?D,D>>D 3/4 D2 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.
The kernel is not OOM. It just failed to allocate for GFP_NOWAIT which
means that no memory reclaim could be used to free up potentially unused
page cache. This means that kswapd is not able to free up memory in the
pace it is allocated. Such an allocation failure shouldn't be critical
and the caller should have means to fall back to a regular allocation or
retry later. You can play with min_free_kbytes and increase it to kick
the background reclaim sooner.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-10-20 9:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 20:16 Михаил Гаврилов
2017-10-19 3:56 ` Du, Changbin
2017-10-19 18:52 ` Михаил Гаврилов
2017-10-20 6:43 ` Du, Changbin
2017-10-20 9:12 ` Michal Hocko [this message]
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=20171020091239.cfwapdkx5g7afyp7@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=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