From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Page Allocation Failures Return With 2.6.9+TSO patch.
Date: Sat, 23 Oct 2004 20:29:28 +1000 [thread overview]
Message-ID: <417A3288.1000303@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.61.0410230558060.639@p500>
Justin Piszcz wrote:
> It does not seem like they do, but they cannot be good...
>
It seems almost inevitable that they'll happen, especially if a module
is loaded after boot (this is actually somewhere that incremental min
will help "echo some number > /proc/sys/vm/lower_zone_protection").
But from the code, the failures really won't hurt at all. It might
double the number of interrupts coming from your soundcard, but I
dare say you would never be able to notice a difference.
> I have applied the following patches
>
> 1] TSO patch
> 2] rollup.patch
>
> Rebooting now and will alert the list if/when I receive more page
> allocation failures.
>
> FYI - I started getting these with 2.6.9.
>
> (However, it was always possible on the Dell Optiplex GX1 to create page
> allocation failure with: ifconfig eth0 mtu 9000), however, on a
> higher-end machine (2.6GHZ, 2GB ram, etc) ifconfig eth0 mtu 9000 worked
> fine.
>
> Is it something with the architecture of the box bus/box?
>
No, probably just different configurations or memory usage patterns
of the kernel, maybe different drivers, etc.
> Why does it tend to affect one machine and not the other?
>
Again, luck of the draw mainly. My patch should definitely help the
TSO allocation failures (it probably won't fix the sound buffer alloc
failure though, now that I've looked at it).
prev parent reply other threads:[~2004-10-23 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 8:35 Page Allocation Failures Return With 2.6.9+TSO patch Justin Piszcz
2004-10-23 9:14 ` Nick Piggin
2004-10-23 9:22 ` Justin Piszcz
2004-10-23 9:32 ` Nick Piggin
2004-10-23 10:02 ` Justin Piszcz
2004-10-23 10:29 ` 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=417A3288.1000303@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=jpiszcz@lucidpixels.com \
--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;
as well as URLs for NNTP newsgroup(s).