linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Alexander Potapenko <glider@google.com>
Cc: Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.cz>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	riel@redhat.com, David Rientjes <rientjes@google.com>,
	mgorman@techsingularity.net
Subject: Re: [mmotm-2016-07-18-16-40] page allocation failure: order:2, mode:0x2000000(GFP_NOWAIT)
Date: Thu, 21 Jul 2016 01:34:27 +0300	[thread overview]
Message-ID: <20160720223427.GA22911@node.shutemov.name> (raw)
In-Reply-To: <CAG_fn=UP0169b+cTxVBhqPUfOurQNxAKne0pYSPy3a1uFvTp-g@mail.gmail.com>

On Wed, Jul 20, 2016 at 08:12:13PM +0200, Alexander Potapenko wrote:
> >>>>> It's easy to reproduce in my setup: virtual machine with some amount of
> >>>>> swap space and try allocate about the size of RAM in userspace (I used
> >>>>> usemem[1] for that).
>
> Am I understanding right that you're seeing allocation failures from
> the stack depot? How often do they happen? Are they reported under
> heavy load, or just when you boot the kernel?

As I described, it happens under memory pressure.

> Allocating with __GFP_NOWARN will help here, but I think we'd better
> figure out what's gone wrong.
> I've sent https://lkml.org/lkml/2016/7/14/566, which should reduce the
> stack depot's memory consumption, for review - can you see if the bug
> is still reproducible with that?

I was not able to trigger the failure with the same test case.
Tested with v2 of the patch.

(Links to http://lkml.kernel.org/ or other archive with message-id in url
is prefered. lkml.org is garbage)

-- 
 Kirill A. Shutemov

--
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>

  reply	other threads:[~2016-07-20 22:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 11:44 [mmotm-2016-07-18-16-40] page allocation failure: order:2, mode:0x2000000(GFP_NOWAIT) Kirill A. Shutemov
2016-07-20 11:53 ` Michal Hocko
2016-07-20 13:39   ` Vlastimil Babka
2016-07-20 15:19     ` Kirill A. Shutemov
2016-07-20 15:33       ` Vlastimil Babka
2016-07-20 18:12         ` Alexander Potapenko
2016-07-20 22:34           ` Kirill A. Shutemov [this message]
2016-07-21 11:33             ` Alexander Potapenko

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=20160720223427.GA22911@node.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=akpm@linux-foundation.org \
    --cc=glider@google.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.cz \
    --cc=riel@redhat.com \
    --cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).