>> > Intersperesed I see some other messages that are new to me: >> > [ 4019.443129] Open BA session requested for 00:0a:79:eb:56:10 tid 0 >> > [ 4019.500149] activated addBA response timer on tid 0 >> > [ 4020.500033] addBA response timer expired on tid 0 > > I guess the delay here is due to the synchronize_net()? That can take a > while, 57ms seems a lot but I suppose it's possible. > >> > [ 4020.501626] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0 >> > [ 4023.740570] switched off addBA timer for tid 0 >> > [ 4023.740578] got addBA resp for tid 0 but we already gave up >> >> Here is the AP is finally replying > > It's kinda hard to believe that the AP took 4 seconds (!) to reply to > the frame. Where could the frame get stuck? I don't see any other work > processing happening etc. either. It's also curious that in those 3 > seconds between these messages, we didn't actually get around to > stopping the session, that only happens just after: > <snip> > > > Could something be hogging the workqueues? > So I tried to understand what is going on with the workqueue and ended up to see that if we are lucky, we can need the workqueue for the BA handshake (could be AddBA / DelBA handling, or driver callback) while we are scanning. Which basically means that we will need to wait until the scan is over to handle these frames / callbacks. I got these measurements while stopping the BA session: * scanning working for roughly 3 seconds (pardon me not being precise, but with this order of magnitude I don't care much about the single millisecond..) * when scanning is over, the while loop in ieee80211_iface_work consumes 73 mgmt for about 34ms. ( how come we have so many beacons during those 3 seconds..., or maybe all the BCAST probe request ?, my network is quite busy...) * then the finally my stop_tx_ba_cb was served which took 10ms (time takes by the driver). * another series of beacons (10ms). -- 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
