public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Michael Clark <michael@metaparadigm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 page allocation failure. order:0, mode:0x20
Date: Thu, 28 Oct 2004 12:51:29 -0700	[thread overview]
Message-ID: <20041028125129.057db7dc.akpm@osdl.org> (raw)
In-Reply-To: <4180FE0A.2020000@metaparadigm.com>

Michael Clark <michael@metaparadigm.com> wrote:
>
> On 10/28/04 17:40, Andrew Morton wrote:
>  > Michael Clark <michael@metaparadigm.com> wrote:
>  >> cc1: page allocation failure. order:0, mode:0x20
>  >>   [<c013ba43>] __alloc_pages+0x1c3/0x390
>  >>   [<c013bc35>] __get_free_pages+0x25/0x40
>  >>   [<c013f283>] kmem_getpages+0x23/0xd0
>  >>   [<c013ffcf>] cache_grow+0xaf/0x160
>  >>   [<c0140202>] cache_alloc_refill+0x182/0x230
>  >>   [<c0140499>] kmem_cache_alloc+0x49/0x50
>  >>   [<c01c07df>] radix_tree_node_alloc+0x1f/0x70
>  >>   [<c01c0aad>] radix_tree_insert+0xed/0x110
>  >>   [<c014d841>] __add_to_swap_cache+0x71/0x100
>  >>   [<c014da5f>] add_to_swap+0x5f/0xc0
>  >>   [<c0142d32>] shrink_list+0x442/0x480
>  >>   [<c014bf7c>] page_referenced_anon+0x7c/0x90
>  >>   [<c01419c8>] __pagevec_release+0x28/0x40
>  > 
>  > 
>  > I'm confused.  2.6.9 uses __GFP_NOWARN in add_to_swap() so the messages
>  > should be suppressed.  Are you sure you're using 2.6.9?
> 
>  Ya is 2.6.9, has uml-skas patch also but that doesn't touch swap_state.c
> 
>  Ah, I see I think, radix_tree_node_alloc first calls kmem_cache_alloc
>  with root->gfp_mask and only if this fails dips into the preloaded
>  percpu node stash.

Oh crap, so it does.

--- 25/mm/swap_state.c~swapper_space-warning-suppression	2004-10-28 12:51:06.975218208 -0700
+++ 25-akpm/mm/swap_state.c	2004-10-28 12:51:15.910859784 -0700
@@ -34,7 +34,7 @@ static struct backing_dev_info swap_back
 };
 
 struct address_space swapper_space = {
-	.page_tree	= RADIX_TREE_INIT(GFP_ATOMIC),
+	.page_tree	= RADIX_TREE_INIT(GFP_ATOMIC|__GFP_NOWARN),
 	.tree_lock	= SPIN_LOCK_UNLOCKED,
 	.a_ops		= &swap_aops,
 	.i_mmap_nonlinear = LIST_HEAD_INIT(swapper_space.i_mmap_nonlinear),
_


      parent reply	other threads:[~2004-10-28 20:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-28  5:31 2.6.9 page allocation failure. order:0, mode:0x20 Michael Clark
2004-10-28  5:56 ` Michael Clark
2004-10-28  6:02   ` Michael Clark
2004-10-28  7:18   ` Daniel Phillips
2004-10-28  8:29 ` Denis Vlasenko
2004-10-28 15:26   ` Michael Clark
2004-10-28  9:40 ` Andrew Morton
2004-10-28 14:11   ` Michael Clark
2004-10-28 14:47     ` Michael Clark
2004-10-28 19:51     ` Andrew Morton [this message]

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=20041028125129.057db7dc.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@metaparadigm.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