[RFC] P2P: send GO neg confirm without wait

Jouni Malinen j
Wed Jun 6 06:40:52 PDT 2012


On Fri, Jun 01, 2012 at 10:46:24AM +0200, Johannes Berg wrote:
> The GO negotiation confirm frame doesn't need
> to be sent with a wait since we don't expect a
> response to it.

Thanks, applied. I was trying to figure out why the wait was there in
the first place, but could not really come up with any good reason for
maintaining this value. I think it ended up coming from the early design
where a hardcoded value was used for all operation and this GO Neg Conf
frame was just never optimized to use something else than the default
200 ms wait. Not that this really should make much of a difference since
the wait is canceled immediately after receiving TX status event from
the driver.

-- 
Jouni Malinen                                            PGP id EFC895FA



More information about the Hostap mailing list