On Feb 4, 2008 5:24 PM, Felix Fietkau <nbd@xxxxxxxxxxx> wrote: > Tomas Winkler wrote: > >> > Maybe we should add blob to tx_status let say of skb->cb[] size and > >> > field for rate scale algorithm version/name. Otherwise we will be > >> > inventing API for each rate scale algorithm... > >> > >> I disagree, we should have something generic enough to allow some sort of > >> "capability negotiation" between the driver and the rate control > >> algorithm, otherwise we could just remove rate control algorithms > >> completely and internalize them into drivers (with some "helper" functions > >> for those who don't want to write their own)... Which I'm sure you might > >> actually like but I don't ;) > > > > So Felix how many rates do you need for each packet? > The algorithm is designed to work with 4 different rates with adjustable > retry counts. A good description can be found here: > http://madwifi.org/browser/madwifi/trunk/ath_rate/minstrel/minstrel.txt > Will this work work you? ieee80211_tx_ratectrl { u32 bitrate ( or pointer to ieee80211_rate I prefer no) u32 flags u32 retry_count } ieee80211_tx_status { ieee80211_tx_ratectrl retry_count[ X] / * X >= 4 */ } Thanks Tomas > - 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
