On Mon, Jul 12, 2010 at 05:17:51PM +0200, Felix Fietkau wrote: > On 2010-07-12 12:48 PM, Ivo Van Doorn wrote: > > The problem here is that we have lost the per-sta statistics. However using the > > single TX status reports, we can count the number of frames which are sent for > > a given STA during the poll interval. We can then determine the percentage of > > frames sent for that STA, We can then add the percentage of the retry and ACK > > count to each STA. Throughout poll interval the rate algorithm would send all > > frames to the same STA with the same TX rate, but between polls, the rate will > > be updated. > > > > Overall these changes will not make the optimal use of PID or > > Minstrel, but it would > > at least improve the situation for USB. > > > > Any thoughts about this solution? > I don't know how minstrel could work with this approach. Before it > starts to use a rate, it has to sample it first. How can you sample > rates with your tx status feedback approach? You would have to commit to that rate for at least one polling period, no? John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- 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
