From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Serban Simu <serban@asperasoft.com>
Cc: linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: page allocation failure & sk98lin
Date: Wed, 25 Aug 2004 12:20:48 +1000 [thread overview]
Message-ID: <412BF780.3090508@yahoo.com.au> (raw)
In-Reply-To: <412BA4FC.2070505@asperasoft.com>
Serban Simu wrote:
> Thank you, Nick. Just wanted to mention that while I understand that we
> recover from this allocation failure (and also I don't mind the stack
> printouts), about 20% of my incoming network traffic (600-700 Mbps)
> seems to be dropped in the process.
Yeah that is expected - so I guess it isn't exactly 'harmless' if
performance is critical.
> Does the memory manager have to
> spend a considerable amount of time to recover?
>
> I will have a look at the -mm fixes, thanks for the idea.
>
The relevant patch is this one which is now merged into 2.6.
http://linux.bkbits.net:8080/linux-2.5/cset@412b8828ClkE2ZwNwGQ02aYoMwb7-A?nav=index.html|ChangeSet@-1d
It would be nice if you can test that. It will give GFP_ATOMIC allocators
a larger buffer between starting memory reclaim, and failing their allocations.
However if it is a production system and you can't test patches, Marcelo
pointed out that you should be able to work around the problem by increasing
/proc/sys/vm/min_free_kbytes. Then maybe you could try 2.6.9 with min_free_kbytes
back to its default setting :)
prev parent reply other threads:[~2004-08-25 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 6:28 page allocation failure & sk98lin Serban Simu
2004-08-24 7:50 ` Nick Piggin
2004-08-24 20:28 ` Serban Simu
2004-08-25 2:20 ` Nick Piggin [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=412BF780.3090508@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=serban@asperasoft.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 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.