From: Eric Dumazet <eric.dumazet@gmail.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: JesseBrandeburg <jesse.brandeburg@intel.com>,
David Miller <davem@davemloft.net>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
Tushar NDave <tushar.n.dave@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jeffrey TKirsher <jeffrey.t.kirsher@intel.com>
Subject: RE: [E1000-devel] [e100] Page allocation failure warning(?) in 2.6.36.3
Date: Thu, 13 Jan 2011 10:05:56 +0100 [thread overview]
Message-ID: <1294909556.3570.25.camel@edumazet-laptop> (raw)
In-Reply-To: <895344.13845.qm@web121707.mail.ne1.yahoo.com>
Le jeudi 13 janvier 2011 à 01:00 -0800, Chris Rankin a écrit :
> --- On Thu, 13/1/11, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> > Problem is e100 allocates an order-6 page in DMA zone
> > (a 256 KB contigous area of ram)
> >
> > This contigous area of ram is not available but just after
> > booting...
>
> I suspected as much. Fortunately, this machine has no function apart from routing and can happily left untouched for extended periods of time.
>
> > On such small router, I doubt you need more than 64 slots
> > in TX ring buffer.
>
> But what would the effect of that change be to the interfaces' performance, please?
If you care of performance, dont unload/reload your driver all the time,
and dont use modules (this matter on old hardware because of TLB misses)
Anyway, the change ( 128 -> 64 ) is not needed, since the kernel message
is a warning only. The allocation is retried and apparently succeeds.
The __GFP_NOWARN should make the failed allocation not noticed at all.
next prev parent reply other threads:[~2011-01-13 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 12:53 [e100] Page allocation failure warning(?) in 2.6.36.3 Chris Rankin
2011-01-10 23:11 ` [E1000-devel] " Dave, Tushar N
2011-01-10 23:41 ` Chris Rankin
2011-01-11 0:37 ` Dave, Tushar N
2011-01-11 8:52 ` [E1000-devel] " Chris Rankin
2011-01-11 20:59 ` Chris Rankin
2011-01-12 17:35 ` Eric Dumazet
2011-01-12 17:42 ` [E1000-devel] " Chris Rankin
2011-01-12 17:48 ` Eric Dumazet
2011-01-12 18:05 ` Brandeburg, Jesse
2011-01-12 18:14 ` Eric Dumazet
2011-01-12 23:27 ` Chris Rankin
2011-01-13 4:55 ` Eric Dumazet
2011-01-13 9:00 ` Chris Rankin
2011-01-13 9:05 ` Eric Dumazet [this message]
2011-01-13 9:24 ` Chris Rankin
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=1294909556.3570.25.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=rankincj@yahoo.com \
--cc=tushar.n.dave@intel.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