[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1361351538.8629.3.camel@jlt4.sipsolutions.net>
Date: Wed, 20 Feb 2013 10:12:18 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Marc MERLIN <marc@...lins.org>, David Miller <davem@...emloft.net>,
Larry.Finger@...inger.net, bhutchings@...arflare.com,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: 3.7.8/amd64 full interrupt hangs due to iwlwifi under big nfs
copies out
On Tue, 2013-02-19 at 08:21 -0800, Eric Dumazet wrote:
> On Tue, 2013-02-19 at 11:03 +0100, Johannes Berg wrote:
> > On Mon, 2013-02-18 at 21:17 -0800, Eric Dumazet wrote:
> >
> > > > chrome: page allocation failure: order:1, mode:0x4020
> > > > Pid: 8730, comm: chrome Tainted: G O 3.7.8-amd64-preempt-20121226-fixwd #1
> > > > Call Trace:
> > > > <IRQ> [<ffffffff810d5f38>] warn_alloc_failed+0x117/0x12c
> >
> > > You could try to load iwlwifi with amsdu_size_8K set to 0 (disable)
> > >
> > > It should hopefully use order-0 pages
> >
> > It will, do that then, unfortunately it can't switch at runtime because
> > it advertised this support to the access point or clients.
>
> What are the drawbacks of setting amsdu_size_8K to 0 by default ?
We're discussing this now, the only downside would be that we couldn't
receive 8k A-MSDUs. Thing is, practically nobody uses A-MSDU anyway, and
even when I suspect the difference between 4k and 8k won't be huge.
johannes
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists