On 2012-01-28 7:43 PM, Marek Lindner wrote: > On Saturday, January 28, 2012 21:25:39 Felix Fietkau wrote: >> On 2012-01-28 8:17 AM, Marek Lindner wrote: >> > Signed-off-by: Marek Lindner <lindner_marek@xxxxxxxx> >> >> NACK, minstrel_ht sets RTS/CTS only from the second rate retry slot on, >> to increase the success probability during retransmissions. For the >> first slot, it is unset. The user supplied rts setting is not suitable >> for configuring RTS/CTS usage this way, so if you want to disable it >> entirely, you'd need to add a new setting for that. > > If you think it is unsuitable do you mind elaborating what this setting is > for? As far as I can tell minstrel_ht is the only rate control algorithm that > decides to be smarter than the user configuring the device. Without mentioning > this anywhere! IMHO it should be minstrel_ht explaining why this makes sense, > not the other way round. The user configurable RTS/CTS setting sets a threshold which is applied to all transmission attempts with a packet size above it. What minstrel_ht does is enable RTS/CTS only for on-chip retransmissions of the second rate slot and below. That means as long as it doesn't fall back to lower rates, no RTS/CTS gets used. It's not about minstrel_ht being smarter than the user. It's about adaptive control of RTS/CTS being smarter than a static setting. - Felix -- 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
