On Fri, 2011-11-11 at 14:16 +0100, Stanislaw Gruszka wrote: > On Wed, Nov 09, 2011 at 02:08:54PM +0100, Johannes Berg wrote: > > How do we want to handle these things? I'm sure I want the drivers to > > handle multi-channel operation fairly transparently, with multiple > > (hardware) queues (in the driver), so mac80211 doesn't have to > > start/stop the queues continuously and can just transmit on that > > interface, the frame might only go out a bit later. > > I do not quite understand how separate tx queues could help here, because > we not only have to transmit off-channel but also receive data. For me > simple solution would be adding new functions on top of > ieee80211_tx_skb, which will just queue skb's if we are not on operating > channel at present, and send them lately when we come back. > > Or perhaps you are talking about separate tx and rx queues, that could > eventually work, but driver still should know how long to stay off-channel > to receive all needed frames. Well, so usually you'd schedule NoA, or use null data frames to not receive, etc. Using multiple TX queues would help schedule the TX, scheduling the RX is a different issue. 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
