From: Eric Dumazet <eric.dumazet@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 16083] New: swapper: Page allocation failure
Date: Thu, 03 Jun 2010 23:58:02 +0200 [thread overview]
Message-ID: <1275602282.2533.72.camel@edumazet-laptop> (raw)
In-Reply-To: <20100603143915.f1b0ba2b.akpm@linux-foundation.org>
Le jeudi 03 juin 2010 à 14:39 -0700, Andrew Morton a écrit :
> Well. The presence of this warning does serve to remind us how sucky
> e1000[e] is :(
>
> I'm not particularly fussed either way - I'm just wondering if you guys
> think this thing meets the noise-to-benefit test...
>
Well, in this particular case, I think its a genuine bug in the ipv6
code, not on the e1000[e] driver :)
It allocates "a priori" dev->mtu sized skb that are filled by maybe one
hundred bytes by caller.
With MTU=9000, this means order-2 allocations. In an ideal world, it
would be fine, but in practice, we know only fools can trust high order
allocations.
Since code is prepared to chain skbs, just make sure we cap allocations
to smaller units (up to 0xe80 bytes on a 64bit kernel)
So in this particular case, the bugzilla report can point to a real
problem in our stack.
Failed allocations had been silent, we probably would never have
noticed.
Hmm...
next prev parent reply other threads:[~2010-06-03 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16083-10286@https.bugzilla.kernel.org/>
2010-06-03 20:02 ` [Bugme-new] [Bug 16083] New: swapper: Page allocation failure Andrew Morton
2010-06-03 21:13 ` Eric Dumazet
2010-06-03 21:37 ` Eric Dumazet
2010-06-03 22:01 ` Andrew Morton
2010-06-05 10:04 ` David Miller
2010-06-03 21:39 ` Andrew Morton
2010-06-03 21:58 ` Eric Dumazet [this message]
2010-06-03 22:11 ` Andrew Morton
2010-06-05 9:59 ` David Miller
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=1275602282.2533.72.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@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