From: Stephen Hemminger <shemminger@vyatta.com>
To: starlight@binnacle.cx, Sony Chacko <sony.chacko@qlogic.com>,
Rajesh Borundia <rajesh.borundia@qlogic.com>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: kernel 3.1.1 message: <IRQ> warn_alloc_failed
Date: Fri, 9 Dec 2011 09:50:14 -0800 [thread overview]
Message-ID: <20111209095014.14a647cd@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <6.2.5.6.2.20111208210303.03a06228@flumedata.com>
On Thu, 08 Dec 2011 21:10:02 -0500
starlight@binnacle.cx wrote:
> Hello.
>
> FYI saw several of these when running
> multiple 'rcp' commands copying multi-gigabyte
> files to/from system.
>
> 'rcp' target files were all on an encrypted
> mirrored USB3-attached pair of 3TB hard
> drives.
>
> One outgoing 'rcp' was to a system with
> a much slower disk (due to a USB2 attachment)
> and that transfer was putting back-pressure
> on the connection.
>
> Kernel is running on a CentOS 6.0
> distribution.
>
> Not subscribing to the lists, so please
> CC me with any queries. Please note that
> email originating from most non-US MTAs
> will bounce, but I will check the list
> archives if I see any.
>
> Can't spend a lot of time on this but am
> willing to answer a few questions. Hopefully
> the call stack will tell the story well
> enough.
You are seeing memory allocation failures because device
is allocating a 16K (order 2) size socket buffer. You are using
netxen device, and it looks like the problem.
>From reading the netxen driver source. The LRO buffers in this device
are very large (8060+skb overhead).
Until the driver is fixed to use fragmented page size memory,
I recommend turning off LRO.
next prev parent reply other threads:[~2011-12-09 17:50 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 [this message]
[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
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=20111209095014.14a647cd@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rajesh.borundia@qlogic.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 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.