2010/12/7 Björn Smedman <bjorn.smed...@venatech.se>: > On Mon, Dec 6, 2010 at 9:14 AM, Bruno Randolf <b...@einfach.org> wrote: > [snip] >> >> Other examples: >> >> *** txdesc tries 2 >> *** mrr 0 tries 9 rate 12 >> *** mrr 1 tries 2 rate 13 >> *** mrr 2 tries 3 rate 11 >> >> = 16 transmissions in sum. >> >> *** txdesc tries 9 >> *** mrr 0 tries 3 rate 11 >> *** mrr 1 tries 9 rate 8 >> *** mrr 2 tries 3 rate 11 >> >> = 24 transmissions in sum. Again, rate[1] and rate[3] are the same, so why >> bother setting it up twice? > > I remember from experimenting with rate control in madwifi that weird > stuff can happens when you go above ATH_TXMAXTRY = 13 tx attempts in > total (all mrr segments combined). We thought we saw some significant > improvement on poor links when we reduced retries to fit the whole mrr > chain into 13 retries in total, but we didn't have the equipment to > really verify that. Perhaps something you could try Jonathan in your > excellent testbed?
I'd be happy to test this if you give me the exact scenario you would like me to run. Incidentally, I didn't set up this testbed, my colleague Konstanty did. You can read about it here: http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=5562247 and a copy of the PDF is accessible from my Dropbox: http://dl.dropbox.com/u/2451223/3836_publication_Design_of__2932.pdf. Cheers, Jonathan > > /Björn > _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
