On Sunday, January 29, 2012 04:20:24 you wrote: > On 2012-01-28 8:58 PM, Marek Lindner wrote: > >> I'm with Felix: I could see adding an option that means "force never > >> use RTS/CTS" but I think we're at the right operating point when > >> interpreting the standard "RTS/CTS threshold" option. > > > > Actually, this option exists already. It's just minstrel_ht overriding > > it: iw phy <phyname> set rts <rts threshold|off> > > Put special attention towards the "off" at the end. > > > > If we let the rate algorithm override our rts settings it should at least > > be communicated. I found no such mention anywhere. > > > > I'd like to further stress the point that no other rate algorithm does > > this. We create incoherent and hard to debug behavior. > > Which rate algorithms did you check to come to that conclusion? I just > looked at the ath9k rate control algorithm and it does the same ;) I checked net/mac80211/rc80211_* since that is where minstrel_ht is living. Regards, Marek -- 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
