From: Serban Simu <serban@asperasoft.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: page allocation failure & sk98lin
Date: Tue, 24 Aug 2004 13:28:44 -0700 [thread overview]
Message-ID: <412BA4FC.2070505@asperasoft.com> (raw)
In-Reply-To: <412AF360.60005@yahoo.com.au>
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. 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.
-Serban
Nick Piggin wrote:
> Serban Simu wrote:
>
>> Hello all,
>>
>> I found a few references to similar problems in the list but no
>> indications of whether this has been fixed or can be avoided.
>>
>> I'm using 2.6.8.1 and the patch: sk98lin_v7.04_2.6.8_patch. This
>> happens when receiving data fast on the GigE card (about 600Mbps) and
>> writing on disk. It seems to happen after writing 1 GB to disk (1024
>> MB) but I can't correlate that very reliably.
>>
>> I would appreciate any information pointing me to a fix or explanation.
>>
>> Thank you!
>>
>> -Serban
>>
>> swapper: page allocation failure. order:0, mode:0x20
>
>
>
> The messages should be basically harmless and can't be completely avoided.
>
> That said, -mm kernels have patches to fix up numerous problems with the
> page
> allocator which have a good chance of fixing your problems.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-08-24 20:27 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 [this message]
2004-08-25 2:20 ` Nick Piggin
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=412BA4FC.2070505@asperasoft.com \
--to=serban@asperasoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.