diff options
author | Luis R. Rodriguez <lrodriguez@atheros.com> | 2008-11-20 17:15:12 -0800 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2008-11-25 16:13:08 -0500 |
commit | ca0c7e5101fd4f37fed8e851709f08580b92fbb3 (patch) | |
tree | 6121ed93a7d14be26b95c3da9eed859f49164a78 /drivers/leds | |
parent | 3dd3b79aeadc6f6abc5cc78724d7df3dfcc1bd0b (diff) | |
download | blackbird-op-linux-ca0c7e5101fd4f37fed8e851709f08580b92fbb3.tar.gz blackbird-op-linux-ca0c7e5101fd4f37fed8e851709f08580b92fbb3.zip |
ath9k: Fix SW-IOMMU bounce buffer starvation
This should fix the SW-IOMMU bounce buffer starvation
seen ok kernel.org bugzilla 11811:
http://bugzilla.kernel.org/show_bug.cgi?id=11811
Users on MacBook Pro 3.1/MacBook v2 would see something like:
DMA: Out of SW-IOMMU space for 4224 bytes at device 0000:0b:00.0
Unfortunately its only easy to trigger on MacBook Pro 3.1/MacBook v2
so far so its difficult to debug (even with swiotlb=force).
We were pci_unmap_single()'ing less bytes than what we called
for with pci_map_single() and as such we were starving
the swiotlb from its 64MB amount of bounce buffers. We remain
consistent and now always use sc->rxbufsize for RX. While at
it we update the beacon DMA maps as well to only use the data
portion of the skb, previous to this we were pci_map_single()'ing
more data for beaconing than what we tell the hardware it can use,
therefore pushing more iotlb abuse.
Still not sure why this is so easily triggerable on
MacBook Pro 3.1, it may be the hardware configuration
tends to use more memory > 3GB mark for DMA.
Signed-off-by: Maciej Zenczykowski <zenczykowski@gmail.com>
Signed-off-by: Bennyam Malavazi <Bennyam.Malavazi@atheros.com>
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/leds')
0 files changed, 0 insertions, 0 deletions