Hi all, Some of us have discussed this before, but I wanted to get some wider dissemination ... With multi-channel, one problem that we get is managing the channel timing for authentication/association. We'll have bound the channel context (once we have that) before we even send a frame of course, but setting up the timing as to when to use the channel is very hard, in particular for connections to P2P GOs that might potentially be asleep. I see a few obvious choices, open for other suggestions. 1) bring back something like the TX sync API, where the driver sleeps until the frame can be transmitted; this is done before every transmit 1a) do the same, but asynchronously (somewhat ugly) 2) sleep in sta_state in the driver; this is problematic because while we know that the auth frame will be sent right after the AP station is created, we don't see the retransmits properly 3) do it in the driver in tx(); this is problematic because it may mean delaying the frames quite a bit, and mac80211 might then try to retransmit too early etc 4) introduce a sleeping mgmt-tx driver call to send such frames; this is ugly in mac80211 code flows with the TX functions 5) do remain-on-channel from mac80211, but this doesn't address P2P GO synchronisation requirements I haven't been able to come up with any other ways, and here we really don't have much of a choice -- #1 is the only thing that seems sane to me. Thoughts? 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
