From: Nick Piggin <nickpiggin@yahoo.com.au>
To: arjanv@redhat.com
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: page allocation failure. order:0, mode:0x20
Date: Sun, 20 Jun 2004 20:54:40 +1000 [thread overview]
Message-ID: <40D56CF0.2040803@yahoo.com.au> (raw)
In-Reply-To: <1087727591.2805.8.camel@laptop.fenrus.com>
Arjan van de Ven wrote:
> On Sun, 2004-06-20 at 12:25, Nick Piggin wrote:
>
>>>| # free
>>>| total used free shared buffers cached
>>>| Mem: 10260 9844 416 0 240 5004
>>>| -/+ buffers/cache: 4600 5660
>>>| Swap: 33256 3796 29460
>>>
>>
>>Not even atomic allocations memory are allowed to consume all memory.
>>A small amount is reserved for memory freeing (which sometimes
>>requires initial memory allocations).
>>
>>The message should be harmless.
>
>
> Since atomic allocations by definition need to be able to cope with
> failure, how about a patch like this to not warn for this common and
> legit case?
>
CC'ed Andrew: I think it's his baby.
I guess we're at the point where we should quiet down things like
this. Although order-0 atomic allocation failures are pretty rare,
I'd consider leaving them in. Maybe a CONFIG option?
next prev parent reply other threads:[~2004-06-20 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 9:20 page allocation failure. order:0, mode:0x20 Geert Uytterhoeven
2004-06-20 10:25 ` Nick Piggin
2004-06-20 10:31 ` Geert Uytterhoeven
2004-06-20 10:33 ` Arjan van de Ven
2004-06-20 10:54 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 14:08 Naveen Burmi
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=40D56CF0.2040803@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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.