On Fri, Jan 06, 2017 at 04:15:40PM +0100, Felix Fietkau wrote: > On 2017-01-06 14:05, Stanislaw Gruszka wrote: > > When medium is busy or frames have to be resend, it takes time to send > > the frames and get TX status from hardware. For some really bad medium > > conditions it can take seconds. Patch change TX status timeout to give > > HW more time to provide it, however 500ms is not enough for bad > > conditions. In the future this timeout should be removed and replaced > > with proper watchdog mechanism. > > > > Increase flush timeout accordingly as well. > > > > Signed-off-by: Stanislaw Gruszka <sgruszka@xxxxxxxxxx> > By the way, to make tx status reporting more robust, I would suggest > mapping tx fifo status to skb only for frames where > IEEE80211_TX_CTL_REQ_TX_STATUS is set. For all other frames, set PID=0 > and return the status using ieee80211_tx_status_noskb. > I did the same in mt76 and it works quite well. Good idea, thanks! Stanislaw
