All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: Evgeniy Polyakov <johnpol@2ka.mipt.ru>, netdev@vger.kernel.org
Subject: Re: page allocation failure
Date: Sat, 14 Jun 2008 22:36:02 +0100	[thread overview]
Message-ID: <20080614213600.GF11300@solarflare.com> (raw)
In-Reply-To: <20080614205958.M55299@visp.net.lb>

Denys Fedoryshchenko wrote:
> There is no jumbo frames in this particular setup.
> Probably it is getting out of memory (rtorrent using almost all for fs caching
> maybe).
[...]

The "order: 3" means an allocation of 8 pages (32 KB) at once, which
should not be needed for receiving standard Ethernet frames.  Looking
at the bnx2 code I can't see any case in which it would allocate an
skb much larger than the MTU.

Network drivers usually try to refill the hardware RX ring immediately
after handling RX completions, at which point they are running in atomic
(non-blocking) context and large contiguous memory allocations are
relatively likely to fail even if the system has plenty of memory.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.

  reply	other threads:[~2008-06-14 21:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14  2:25 page allocation failure Denys Fedoryshchenko
2008-06-14  6:58 ` Evgeniy Polyakov
2008-06-14 21:02   ` Denys Fedoryshchenko
2008-06-14 21:36     ` Ben Hutchings [this message]
2008-06-15  6:04     ` Evgeniy Polyakov
  -- strict thread matches above, loose matches on Subject: below --
2012-07-30 13:25 Shawn Joo
2012-07-30 14:13 ` Michal Hocko
2012-07-31  5:32   ` Shawn Joo
2012-07-31 13:52     ` Michal Hocko
2010-04-06 12:15 kvm
2010-04-06 10:59 ` Thomas Mueller
2010-04-06 13:46   ` kvm
2004-11-11 10:11 sai srinivas dharanikota
2004-11-12  8:32 ` Keir Fraser
2004-08-24 20:05 Dominik Karall
2004-08-24 20:05 ` Andrew Morton
2004-08-24 22:57   ` David S. Miller
2004-01-19 11:36 Oliver Kiddle
2004-01-19 14:54 ` Mike Fedyk
2004-01-19 17:29   ` Oliver Kiddle
2004-01-19 18:12     ` Mike Fedyk
2004-01-20  3:38 ` Andrew Morton
2004-01-20  6:00   ` Nathan Scott
2004-01-20 17:08   ` Oliver Kiddle
2004-01-20 18:35     ` Mike Fedyk
2004-01-22  9:29       ` Oliver Kiddle
2004-01-22  9:59         ` Andrew Morton

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=20080614213600.GF11300@solarflare.com \
    --to=bhutchings@solarflare.com \
    --cc=denys@visp.net.lb \
    --cc=johnpol@2ka.mipt.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.