On Mon, Feb 27, 2012 at 4:46 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2012-02-27 at 16:38 +0100, Helmut Schaa wrote: >> On Mon, Feb 27, 2012 at 12:49 PM, Johannes Berg >> <johannes@xxxxxxxxxxxxxxxx> wrote: >> > Then of course, the driver needs to tell mac80211 about queue mapping. >> > For this, there's one global queue: >> > * off-channel TX queue >> > Additionally, there are per-interface queues: >> > * 4 per AC >> > * CAB for this interface >> >> Ralink devices have only the 4 hw queues and no CAB queue. So, would >> each interface point to the same hw queue or would the driver have to do >> some sort of translation? > > No, just like today I'd expect each interface to point to the same hw > queue. In fact, even in devices that do have more queues I would expect > multiple interfaces to point to the same hw queue, if they share > channels. > > This will be somewhat tricky when an the mapping isn't static, but for > that the netdev queues can be stopped and then the reassignment is > probably not so much of a problem. Ok. >> Also Ralink devices don't have a CAB queue :) > > You just said that ;-) > > But in that case I suppose the CAB queue would simply point to the BE > queue or so as well. But I think they are also quite broken wrt. sending > multicast-after-DTIM anyway, no? Yep, that's done in a tasklet using the BE queue at the moment. Not the perfect solution ... In any case I'd then expect this to > either point to a "virtual" queue that the driver simply has in > software, or to the real BE queue, depending on the desired queue-full > semantics. Ok, fine with me. Helmut -- 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
