> > > It seems to me that this should be per-virtual interface instead of > > > per-hardware? I guess ultimately it won't make a difference because the > > > RA will be unique but I think we should still keep it per-vif where it > > > makes sense. > > > > > I can pass only vif in all the API i give, and that's something that i > > am not sure about since you introduced vif - generally all functions > > can get hw just from having the vif, but still there are plenty of > > places in the code that i see hw being passed back and forth. is it > > just because API compatibility or because something else i need to > > consider? > > Basically I'm thinking that everything that could in theory be > per-interface should be getting a vif. Say you have a multi-BSS AP. I > don't think it's really legal for a STA to associate to multiple APs at > the same time but want to avoid the code falling over when a STA > actually does associate to multiple of our virtual BSSes... Maybe that's > just unnecessary. > I am not sure about the necessity of it myself, as once A-MPDU is active all traffic for the RA/TID (no matter what interface usese it) should be aggregated. I will currently leave it this way, and if you see any problem please describe it specifically and i will change it either on this patch or on top of it. - 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
