b43: Refresh RX poison on buffer recycling
PATCH 1/1 b43: Refresh RX poison on buffer recycling
The RX buffer poison needs to be refreshed, if we recycle an RX buffer, because it might be (partially) overwritten by some DMA operations.
---
Francesco, please stresstest this on top of the other patch that adds poisoning. John, please queue as bugfix.
drivers/net/wireless/b43/dma.c +11 -10
@@ -1503,20 +1503,16 @@ static void dma_rx(struct b43_dmaring *r len =le16_to_cpu (rxhdr->frame_len); }while (len ==0 && i++ <5 );if (unlikely (len ==0 )) { -/* recycle the descriptor buffer. */ -sync_descbuffer_for_device (ring, meta->dmaaddr, - ring->rx_buffersize); - goto drop; + dmaaddr = meta->dmaaddr; + goto drop_recycle_buffer; } }if (unlikely (b43_rx_buffer_is_poisoned (ring, skb))) {/* Something went wrong with the DMA. * The device did not touch the buffer and did not overwrite the poison. */ b43dbg (ring->dev->wl,"DMA RX: Dropping poisoned buffer.\n" ); -/* recycle the descriptor buffer. */ -sync_descbuffer_for_device (ring, meta->dmaaddr, - ring->rx_buffersize); - goto drop; + dmaaddr = meta->dmaaddr; + goto drop_recycle_buffer; }if (unlikely (len > ring->rx_buffersize)) {/* The data did not fit into one descriptor buffer
@@ -1530,6 +1526,7 @@ static void dma_rx(struct b43_dmaring *rwhile (1 ) { desc = ops->idx2desc (ring, *slot, &meta);/* recycle the descriptor buffer. */ +b43_poison_rx_buffer (ring, meta->skb);sync_descbuffer_for_device (ring, meta->dmaaddr, ring->rx_buffersize); *slot =next_slot (ring, *slot);
@@ -1548,8 +1545,7 @@ static void dma_rx(struct b43_dmaring *r err =setup_rx_descbuffer (ring, desc, meta,GFP_ATOMIC );if (unlikely (err)) {b43dbg (ring->dev->wl,"DMA RX: setup_rx_descbuffer() failed\n" ); -sync_descbuffer_for_device (ring, dmaaddr, ring->rx_buffersize); - goto drop; + goto drop_recycle_buffer; }unmap_descbuffer (ring, dmaaddr, ring->rx_buffersize,0 );
@@ -1559,6 +1555,11 @@ static void dma_rx(struct b43_dmaring *rb43_rx (ring->dev, skb, rxhdr); drop:return ; + +drop_recycle_buffer: +/* Poison and recycle the RX buffer. */ +b43_poison_rx_buffer (ring, skb); +sync_descbuffer_for_device (ring, dmaaddr, ring->rx_buffersize); }void b43_dma_rx (struct b43_dmaring *ring)
Signature · 1 line
Greetings, Michael.
Quoted 10 lines · Michael Buesch
The RX buffer poison needs to be refreshed, if we recycle an RX buffer, because it might be (partially) overwritten by some DMA operations.
Cc Francesco Gringoli <[email protected]>Signed-off-by Michael Buesch <[email protected]>---
Francesco, please stresstest this on top of the other patch that adds poisoning.
Hi Michael,
great work! No more crashes with the two patches. I will continue stress testing anyway but it seems stable.
I have one more question: the hardware seems to allow frames that are longer than 2352 bytes. If we monitor the firmware during receiving we get up to 0x1005 bytes long frames. When such frames arrives, the kernel drops them as the "The data did not fit into one descriptor buffer and is split over multiple buffers." I tried to increase B43_DMA0_RX_BUFFERSIZE up to 0x1006 but I get problems with dma and the driver keeps restarting the hardware forever. What is wrong with increasing this value above IEEE80211_MAX_FRAME_LEN?
Many thanks,
Cheers
-FG
Quoted 65 lines
John, please queue as bugfix.
Index:
wireless-testing/drivers/net/wireless/b43/dma.c
===================================================================
---wireless-testing.orig/drivers/net/wireless/b43/dma.c2009-03-27
23:15:36.000000000 +0100
+++wireless-testing/drivers/net/wireless/b43/dma.c2009-03-27
23:30:17.000000000 +0100drivers/net/wireless/b43/dma.c +2
-4@@ -1503,20 +1503,16 @@ static void dma_rx(struct b43_dmaring *r len =le16_to_cpu (rxhdr->frame_len); }while (len ==0 && i++ <5 );if (unlikely (len ==0 )) { -/* recycle the descriptor buffer. */ -sync_descbuffer_for_device (ring, meta->dmaaddr, - ring->rx_buffersize); - goto drop; + dmaaddr = meta->dmaaddr; + goto drop_recycle_buffer; } }if (unlikely (b43_rx_buffer_is_poisoned (ring, skb))) {/* Something went wrong with the DMA. * The device did not touch the buffer and did not overwrite the poison. */
b43dbg(ring->dev->wl, "DMA RX: Dropping poisoned buffer.\n");drivers/net/wireless/b43/dma.c +2
-4-/* recycle the descriptor buffer. */ -sync_descbuffer_for_device (ring, meta->dmaaddr, - ring->rx_buffersize); - goto drop; + dmaaddr = meta->dmaaddr; + goto drop_recycle_buffer;} if (unlikely(len > ring->rx_buffersize)) { /* The data did not fit into one descriptor bufferdrivers/net/wireless/b43/dma.c +2
-2@@ -1530,6 +1526,7 @@ static void dma_rx(struct b43_dmaring *rwhile (1 ) { desc = ops->idx2desc (ring, *slot, &meta);/* recycle the descriptor buffer. */ +b43_poison_rx_buffer (ring, meta->skb);sync_descbuffer_for_device (ring, meta->dmaaddr, ring->rx_buffersize); *slot =next_slot (ring, *slot);@@ -1548,8 +1545,7 @@ static void dma_rx(struct b43_dmaring *r err =setup_rx_descbuffer (ring, desc, meta,GFP_ATOMIC );if (unlikely (err)) {b43dbg (ring->dev->wl,"DMA RX: setup_rx_descbuffer() failed\n" ); -sync_descbuffer_for_device (ring, dmaaddr, ring->rx_buffersize); - goto drop; + goto drop_recycle_buffer; }unmap_descbuffer (ring, dmaaddr, ring->rx_buffersize,0 );@@ -1559,6 +1555,11 @@ static void dma_rx(struct b43_dmaring *rb43_rx (ring->dev, skb, rxhdr);drop:
return;drivers/net/wireless/b43/dma.c +5
-0+ +drop_recycle_buffer: +/* Poison and recycle the RX buffer. */ +b43_poison_rx_buffer (ring, skb); +sync_descbuffer_for_device (ring, dmaaddr, ring->rx_buffersize);}
Quoted 4 lines
void
b43_dma_rx(struct b43_dmaring *ring)Signature · 1 line
Greetings, Michael.
-------
Francesco Gringoli, PhD - Assistant Professor
Dept. of Electrical Engineering for Automation
University of Brescia
via Branze, 38
25123 Brescia
ITALY
Ph: ++39.030.3715843 FAX: ++39.030.380014 WWW: http://www.ing.unibs.it/~gringoli
Quoted 8 lines · On Monday 30 March 2009 23:35:34 Francesco Gringoli wrote:
I have one more question: the hardware seems to allow frames that are longer than 2352 bytes. If we monitor the firmware during receiving we get up to
0x1005bytes long frames. When such frames arrives, the kernel drops them as the "The data did not fit into one descriptor buffer and is split over multiple buffers." I tried to increaseB43_DMA0_RX_BUFFERSIZEup to0x1006but I get problems with dma and the driver keeps restarting the hardware forever. What is wrong with increasing this value aboveIEEE80211_MAX_FRAME_LEN?
Well... First thing is that I think the hardware wasn't ever tested with frames >IEEE80211_MAX_FRAME_LEN. So there might be silicon bugs.
The maximum number of bytes one descriptor can carry is 8191 bytes (not including RX headers and padding. That's 30 bytes).
Third thing is that the buffer must not cross a page boundary. So that is 4096 bytes on most machines. So in practice the 4096 bytes boundary (minus 30 bytes for headers/padding) is upper bound for B43_DMA0_RX_BUFFERSIZE.
Signature · 1 line
Greetings, Michael.