public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "linuxkernel2.20.sandos@spamgourmet.com" 
	<majsetvger.100.sandos@spamgourmet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: E1000 - page allocation failure - saga continues :( message 1 of 20)
Date: Tue, 10 May 2005 19:44:26 +1000	[thread overview]
Message-ID: <4280827A.9080108@yahoo.com.au> (raw)
In-Reply-To: <42807FC6.10400@spamgourmet.com>

linuxkernel2.20.sandos@spamgourmet.com wrote:
> Nick Piggin - nickpiggin@yahoo.com.au wrote:
> 
>> linuxkernel2.20.sandos@spamgourmet.com wrote:

>>> It would be nice with a "cleaner" solution though.
>>>
>>
>> What kernel are you using?
>> Are you doing a lot of block IO as well?
> 
> 
> I am using 2.6.11.8.
> 
> Yes, the server is a fileserver for both the internet (~10Mbit) and 
> internally (1Gbit e1000). Hardware is pretty old so is pretty heavily 
> loaded and with 256MB RAM.
> 

OK, well there are some patches in 2.6.12 that should make
things slightly better, and then some more patches in -mm
(not sure if they'll make it for 2.6.12) that should make
things slightly better again.

Basically they work towards reducing the memory allocation
"priority" for block IO requests, in relation to networking
and other atomic allocation requirements.

If you can't test the latest -mm, or 2.6.12-rc4, then wait
for 2.6.12 and 2.6.13 and check back on the problem.

Thanks,
Nick

-- 
SUSE Labs, Novell Inc.


      reply	other threads:[~2005-05-10  9:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10  8:06 E1000 - page allocation failure - saga continues :( linuxkernel2.20.sandos
2005-05-10  8:19 ` Nick Piggin
2005-05-10  9:32   ` E1000 - page allocation failure - saga continues :( message 1 of 20) linuxkernel2.20.sandos@spamgourmet.com
2005-05-10  9:44     ` 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=4280827A.9080108@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=majsetvger.100.sandos@spamgourmet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox