On Saturday 25 April 2009 09:42:29 Johannes Berg wrote: > On Fri, 2009-04-24 at 21:35 +0200, Christian Lamparter wrote: > > + .ampdu_factor = 3, \ > > + .ampdu_density = 6, \ > > FWIW, I also tried some varying values. This should indicate what you're > able to receive though, not what you're able to transmit since you > control that anyway. yeah... in fact the _correct_ value according to otus is 0 (unrestricted), however that's a bit hard to believe... and ath9k's (not the same mac... I know) default works rather well. [I see about 65 Mbits sustainable throughput and peaks in the lower 80.] > I think we currently don't have a setting though for what to transmit with... > this might need to be added somewhere depending on the RA. well, there should be a table or some bits in phy_control for this purpose... But it looks like otus only has this single MAC knob and the safest setting otus allows is 7 = 8us... of course it would be nice if ieee80211_bss_ht_conf in bss_conf, could be replaced by ieee80211_sta_ht_cap which has the necessary elements. after all this chip was designed as a client adapter, so there's no need to handle multiple a-mpdu density at the same time... Regards, Chr -- 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
