On 2016-03-03 16:37, Johannes Berg wrote: > On Thu, 2016-03-03 at 16:11 +0100, Felix Fietkau wrote: >> >> For my own uses, I'd be perfectly fine with limiting A-MSDU size to >> HT limits even when using VHT - in fact I did that in an early RFC >> patch. I mainly relaxed the limit for VHT based on Emmanuel's >> feedback. I also have doubts about the value of A-MSDU size beyond >> 4095 bytes. >> >> Just let me know which way you'd like it, and I'll send v3 >> accordingly. >> > > I don't really know, I can live with both ways. I'm just a bit worried > that we make enabling this feature so complex that nobody will get it > right. > > Perhaps we could also just remove this, make the default > for max_rc_amsdu_len be 4095 (or so) and leave the rest to the rate > control? We could entirely remove this check here, and let minstrel > only use higher values if VHT is supported (and consequently will be > used)? Yeah, that makes sense.
- Felix -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
