* [PATCH] mac80211: explain TX retry and status
@ 2009-08-07 14:23 Johannes Berg
0 siblings, 0 replies; only message in thread
From: Johannes Berg @ 2009-08-07 14:23 UTC (permalink / raw)
To: John Linville; +Cc: nbd, linux-wireless
Add some more documentation including an example so that
it's clearer what should be done for TX retries.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
---
include/net/mac80211.h | 15 +++++++++++++++
1 file changed, 15 insertions(+)
--- wireless-testing.orig/include/net/mac80211.h 2009-08-07 16:18:15.000000000 +0200
+++ wireless-testing/include/net/mac80211.h 2009-08-07 16:22:21.000000000 +0200
@@ -338,6 +338,21 @@ enum mac80211_rate_control_flags {
*
* When used for transmit status reporting, the driver should
* always report the rate along with the flags it used.
+ *
+ * &struct ieee80211_tx_info contains an array of these structs
+ * in the control information, and it will be filled by the rate
+ * control algorithm according to what should be sent. For example,
+ * if this array contains, in the format { <idx>, <count> } the
+ * information
+ * { 3, 2 }, { 2, 2 }, { 1, 4 }, { -1, 0 }, { -1, 0 }
+ * then this means that the frame should be transmitted
+ * up to twice at rate 3, up to twice at rate 2, and up to four
+ * times at rate 1 if it doesn't get acknowledged. Say it gets
+ * acknowledged by the peer after the fifth attempt, the status
+ * information should then contain
+ * { 3, 2 }, { 2, 2 }, { 1, 1 }, { -1, 0 } ...
+ * since it was transmitted twice at rate 3, twice at rate 2
+ * and once at rate 1 after which we received an acknowledgement.
*/
struct ieee80211_tx_rate {
s8 idx;
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-08-07 14:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-08-07 14:23 [PATCH] mac80211: explain TX retry and status Johannes Berg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).