On Thu, 2013-01-31 at 14:28 +0100, Johannes Berg wrote: > From: Johannes Berg <johannes.berg@xxxxxxxxx> > > When sending authentication/association frames they > might take a bit of time to go out because we may > have to synchronise with the AP, in particular in > the case where it's really a P2P GO. In this case > the 200ms fixed timeout could potentially be too > short if the beacon interval is relatively large. > > For drivers that report TX status we can do better. > Instead of starting the timeout directly, start it > only when the frame status arrives. Since then the > frame was out on the air, we can wait shorter (the > typical response time is supposed to be 30ms, wait > 100ms.) Also, if the frame failed to be transmitted > try again right away instead of waiting. Applied. johannes -- 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
