On Sunday, January 29, 2012 04:26:29 Daniel Halperin wrote: > >> Can you explain what the low-level behavior of an RTS/CTS "battle" is? > >> > >> Abstractly, the behavior you're describing sounds like a buggy driver > >> that doesn't obey overheard RTS or CTS packets. > > > > I certainly can explain it but this is for another thread and unrelated > > to the points raised before. > > Frankly, the correctness of your argument depend on whether there's a > bug or not. If the difference is -2% normally and +300% in bad > interference conditions, you're going to lose this debate. If the > difference is legitimately -99% normally, you might win. I don't quite follow you here. Are you saying it should only be possible to disable rts/cts if I currently have a bug in my rts/cts implementation ? Keep in mind that I am not asking to disable/ban rts/cts for everyone. I'd like minstrel_ht to not override my rts/cts setting if I wish to disable it. 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
