mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Dominik Karall <dominik.karall@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: page allocation failure
Date: Tue, 24 Aug 2004 13:05:31 -0700	[thread overview]
Message-ID: <20040824130531.3cbb03d1.akpm@osdl.org> (raw)
In-Reply-To: <200408242205.20571.dominik.karall@gmx.net>

Dominik Karall <dominik.karall@gmx.net> wrote:
>
> is this a kernel bug, or smbd failure? I think it could be caused by kernel 
>  and less memory. Cause the machine is running with 56MB ram. But IMHO I think 
>  the kernel shouldn't handle it this way. Running 2.6.8-rc4-mm1.

It's networking trying to allocate eight physically-contiguous pages with
GFP_ATOMIC.  Can you say "snowball's chance in hell"?

Probably we should kill off those noisy printk's, or make them dependent on
some debugging option.  But we keep on finding quite serious cases, such as
this one.

Sure, networking will recover from memory allocation failures - presumably
by dropping a packet.  But if it's doing frequent atomic 3-order allocations
then it will end up dropping a *lot* of packets, and performance will suffer.

  reply	other threads:[~2004-08-24 20:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 20:05 Dominik Karall
2004-08-24 20:05 ` Andrew Morton [this message]
2004-08-24 22:57   ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2004-01-19 11:36 Oliver Kiddle
2004-01-19 14:54 ` Mike Fedyk
2004-01-19 17:29   ` Oliver Kiddle
2004-01-19 18:12     ` Mike Fedyk
2004-01-20  3:38 ` Andrew Morton
2004-01-20  6:00   ` Nathan Scott
2004-01-20 17:08   ` Oliver Kiddle
2004-01-20 18:35     ` Mike Fedyk
2004-01-22  9:29       ` Oliver Kiddle
2004-01-22  9:59         ` 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=20040824130531.3cbb03d1.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=dominik.karall@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome