All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 page allocation failure. order:0, mode:0x20
Date: Thu, 28 Oct 2004 22:47:04 +0800	[thread overview]
Message-ID: <41810668.1050800@metaparadigm.com> (raw)
In-Reply-To: <4180FE0A.2020000@metaparadigm.com>

On 10/28/04 22:11, Michael Clark wrote:
> On 10/28/04 17:40, Andrew Morton wrote:
>>
>> 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. Perhaps root->gfp_mask has !__GFP_NOWARN
> 
> Shouldn't it use the preloaded nodes that have been reserved anyway.

 From my other traces - looks like as_get_io_context also needs to use
__GFP_NOWARN in get_io_context as a NULL return appears to be handled.
This is the only other noise i'm getting in my tests.

~mc

  reply	other threads:[~2004-10-28 14:48 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 [this message]
2004-10-28 19:51     ` Andrew Morton

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=41810668.1050800@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.