From: Ben Hutchings <bhutchings@solarflare.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Rajesh Borundia <rajesh.borundia@qlogic.com>,
"starlight@binnacle.cx" <starlight@binnacle.cx>,
Sony Chacko <sony.chacko@qlogic.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: kernel 3.1.1 message: <IRQ> warn_alloc_failed
Date: Tue, 13 Dec 2011 19:09:54 +0000 [thread overview]
Message-ID: <1323803394.2790.5.camel@bwh-desktop> (raw)
In-Reply-To: <20111213104152.14c01911@nehalam.linuxnetplumber.net>
On Tue, 2011-12-13 at 10:41 -0800, Stephen Hemminger wrote:
> On Tue, 13 Dec 2011 11:42:13 -0600
> Rajesh Borundia <rajesh.borundia@qlogic.com> wrote:
>
> > Hi All,
> >
> > Sorry for late reply.
> >
> > Stephan,
> > Thanks for analyzing.
> >
> > Yes, the netxen adapter does not support fragmented page memory.
> > They are not harmful messages. At that instant of time it may fail allocating
> > memory for some buffers in the ring but after enough memory is available
> > it will try to allocate memory for unallocated buffers in ring.
> >
> > Or the other option could be to turn LRO off.
[...]
> The driver should be changed to call allocation with __GFP_NOWARN.
> Change dev_alloc_skb(size) to
> __dev_alloc_skb(size, GFP_ATOMIC|__GFP_NOWARN)
>
> Or better yet, switch to using netdev_alloc variant like
> __netdev_alloc_skb_ip_align(dev, length, GFP_ATOMIC|__GFP_NOWARN)
Why should this be done only in specific drivers?
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2011-12-13 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 2:10 kernel 3.1.1 message: <IRQ> warn_alloc_failed starlight
2011-12-09 17:50 ` Stephen Hemminger
[not found] ` <20111209095014.14a647cd@nehalam.linuxnetplumber.net >
2011-12-09 18:03 ` starlight
2011-12-13 17:42 ` Rajesh Borundia
2011-12-13 18:41 ` Stephen Hemminger
2011-12-13 19:09 ` Ben Hutchings [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=1323803394.2790.5.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rajesh.borundia@qlogic.com \
--cc=shemminger@vyatta.com \
--cc=sony.chacko@qlogic.com \
--cc=starlight@binnacle.cx \
/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).