On 04/09/2012 01:37 PM, David Miller wrote:
From: Marc MERLIN<marc@xxxxxxxxxxx>
Date: Mon, 9 Apr 2012 11:36:32 -0700
On Mon, Apr 09, 2012 at 02:12:41PM -0400, David Miller wrote:
From: Marc MERLIN<marc@xxxxxxxxxxx>
Date: Mon, 9 Apr 2012 10:20:51 -0700
Any idea what's going on, what bucket of RAM is an issue for the driver
(total RAM is more than plenty), and where I should go from there?
The wireless layer is allocating high-order pages, so it's
not the amount of ram, it's the fragmentation of it leading
to a lack of those high-order pages.
I figured it was something of the sort, thanks for the professional
confirmation :)
What's my next step, file a bug with a specific team?
Wait patiently for a wireless developer to look into your bug.
As it happens with both iwlwifi and e1000e, it seems to be a problem further up
the food chain.
I don't know much about iwlwifi, but loading it with the module parameter
"amsdu_size_8K=0" seems to select 4K rather than 8K buffers. That will hurt
performance, but it should fix the memory fragmentation. There have also been
some problems with aggregation that are fixed by setting the option "11n_disable=3".
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
