From: Andrew Morton <akpm@osdl.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: xhejtman@mail.muni.cz, linux-kernel@vger.kernel.org
Subject: Re: 2.6.9 - e1000 - page allocation failed
Date: Fri, 22 Oct 2004 02:51:58 -0700 [thread overview]
Message-ID: <20041022025158.7737182c.akpm@osdl.org> (raw)
In-Reply-To: <20041021225825.GA10844@electric-eye.fr.zoreil.com>
Francois Romieu <romieu@fr.zoreil.com> wrote:
>
> Lukas Hejtmanek <xhejtman@mail.muni.cz> :
> [page allocation failure with e1000]
>
> If you are using TSO, try patch below by Herbert Xu (available
> from http://marc.theaimsgroup.com/?l=linux-netdev&m=109799935603132&w=3)
>
> --- 1.67/net/ipv4/tcp_output.c 2004-10-01 13:56:45 +10:00
> +++ edited/net/ipv4/tcp_output.c 2004-10-17 18:58:47 +10:00
> @@ -455,8 +455,12 @@
> {
> struct tcp_opt *tp = tcp_sk(sk);
> struct sk_buff *buff;
> - int nsize = skb->len - len;
> + int nsize;
> u16 flags;
> +
> + nsize = skb_headlen(skb) - len;
> + if (nsize < 0)
> + nsize = 0;
>
> if (skb_cloned(skb) &&
> skb_is_nonlinear(skb) &&
I'd be interested in knowing if this fixes it - I don't expect it will,
because that's a zero-order allocation failure. He's really out of memory.
The e1000 driver has a default rx ring size of 256 which seems a bit nutty:
a back-to-back GFP_ATOMIC allocation of 256 skbs could easily exhaust the
page allocator pools.
Probably this machine needs to increase /proc/sys/vm/min_free_kbytes.
next prev parent reply other threads:[~2004-10-22 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 22:16 2.6.9 - e1000 - page allocation failed Lukas Hejtmanek
2004-10-21 22:58 ` Francois Romieu
2004-10-22 9:51 ` Andrew Morton [this message]
2004-10-22 12:08 ` Lukas Hejtmanek
2004-10-22 12:45 ` Nick Piggin
2004-12-03 18:37 ` Lukas Hejtmanek
2004-11-03 13:22 ` Lukas Hejtmanek
2004-11-03 14:10 ` Lukas Hejtmanek
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 10:55 Piszcz, Justin Michael
2004-10-22 19:35 ` Francois Romieu
2004-10-22 11:16 Piszcz, Justin Michael
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=20041022025158.7737182c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=xhejtman@mail.muni.cz \
/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).