/[base]
ViewVC logotype

Revision 235461


Jump to revision: Previous Next
Author: adrian
Date: Tue May 15 04:55:15 2012 UTC (12 years, 1 month ago)
Changed paths: 1
Log Message:
Handle non-xretry errors the same as xretry errors for now.

Although I _should_ handle the other errors in various ways (specifically
errors like FILT), treating them as having transmitted successfully
is completely wrong.  Here, they'd be counted as successful and the BAW
would be advanced.. but the RX side wouldn't have received them.

The specific errors I've been seeing here are HAL_TXERR_FILT.

This patch does fix the issue - I've tested it using -i 0.001 pings
(enough to start aggregation) and now the behaviour is correct:

* The RX side never sees a "moved window" error, and
* The TX side sends BARs as needed, with the RX side correctly handling
  them.

PR:		kern/167902


Changed paths

Path Details
Directoryhead/sys/dev/ath/if_ath_tx.c modified , text changed

  ViewVC Help
Powered by ViewVC 1.1.27