From: Evgeniy Polyakov <zbr@ioremap.net>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Maurice Volaski <mvolaski@aecom.yu.edu>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: swapper: page allocation failure. order:2, mode:0x4020 in 2.6.27
Date: Thu, 8 Jan 2009 07:44:31 +0300 [thread overview]
Message-ID: <20090108044431.GA16272@ioremap.net> (raw)
In-Reply-To: <20090108100917.65F3.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Hi.
On Thu, Jan 08, 2009 at 10:19:23AM +0900, KOSAKI Motohiro (kosaki.motohiro@jp.fujitsu.com) wrote:
> if stack dump has tg3_alloc_rx_skb(), that isn't bug. (maybe)
> tg3 network card often reqire non order-0 pages under irq/softirq context.
>
> but linux memory manager can't drop any cache under irq/softirq context.
> therefore the allocation failure is relatively typical.
>
> the allocation failure in packet receive (tg3_alloc_rx_skb) cause
> packet dropping and network peer resend the same packet.
> it decrease network performance a bit. but it doesn't cause any serious problem.
>
> last problem is, why we should look this false-positive warning repeatedly.
>
>
> net-guys, if I say false thing, please fix.
You are right. You repeatedly get that message likely because of jumbo
frames enabled and fragmented ram which does not allow to allocate more
than order-0 pages.
--
Evgeniy Polyakov
prev parent reply other threads:[~2009-01-08 4:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a06240403c58ae633aba5@[129.98.90.227]>
2009-01-08 1:19 ` swapper: page allocation failure. order:2, mode:0x4020 in 2.6.27 KOSAKI Motohiro
2009-01-08 4:44 ` Evgeniy Polyakov [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=20090108044431.GA16272@ioremap.net \
--to=zbr@ioremap.net \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mvolaski@aecom.yu.edu \
--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;
as well as URLs for NNTP newsgroup(s).