| commit | c3a16f278713ad6654f2e5b28e8db5cf60d10884 | |
| author | sephe <sephe> | |
| Mon, 19 Mar 2007 13:38:43 +0000 (19 13:38 +0000) | ||
| committer | sephe <sephe> | |
| Mon, 19 Mar 2007 13:38:43 +0000 (19 13:38 +0000) | ||
| tree | a44d312af67a533edc82cd3f275ebb7e4eeebaec | treesnapshot (tar.gz zip) |
| parent | 9f0b55e91bba0a474423a8a1040c81d2ce0965c5 | commitdiff |
Rename "short/long" retry counter to "data/rts" retry counter. The
original names are inherited from ath(4)'s rate control algorithms,
while ath(4) actually uses short retry counter as rts retry counter,
and long retry counter as data retry counter. According to the short
retry counter usage in 802.11 standard, it can be used as data retry
counter too. Using the "short/long" retry counter is confusing (yah,
I was confused) and most hardwares seem to provide "data/rts" retry
counter, so switch to the new name: "data/rts" retry counter.
This change does not affect ONOE/AMRR TX rate control algorithms
operation in netproto/802_11, but it paves the way for Sample TX rate
control algorithm.
original names are inherited from ath(4)'s rate control algorithms,
while ath(4) actually uses short retry counter as rts retry counter,
and long retry counter as data retry counter. According to the short
retry counter usage in 802.11 standard, it can be used as data retry
counter too. Using the "short/long" retry counter is confusing (yah,
I was confused) and most hardwares seem to provide "data/rts" retry
counter, so switch to the new name: "data/rts" retry counter.
This change does not affect ONOE/AMRR TX rate control algorithms
operation in netproto/802_11, but it paves the way for Sample TX rate
control algorithm.