Hi!
While investigating a case of intermittent extreme packet loss, I've
found that minstrel_ht algo has one possible regression compared to
non-HT version of minstrel. It does not add lowest rate to the last
element of rate table array.
Minstrel:
/* Use lowest rate last */
ratetbl->rate[i].idx = mi->lowest_rix;
ratetbl->rate[i].count = mp->max_retry;
ratetbl->rate[i].count_cts = mp->max_retry;
ratetbl->rate[i].count_rts = mp->max_retry;
Minstrel HT:
rates->rate[i].idx = -1;
This difference can be easily patched. I have two otherwise identical
ath9k-based stations under test for the last two days sitting in the
same noisy environment. So far, patched one seems to be more robust.
Is this difference an intentional design decision or should I submit the patch?
--
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
