ieee80211_tx_info_clear_status(9) [centos man page]

IEEE80211_TX_INFO_CL(9) 				  The basic mac80211 driver inte				   IEEE80211_TX_INFO_CL(9)

NAME

       ieee80211_tx_info_clear_status - clear TX status

SYNOPSIS

       void ieee80211_tx_info_clear_status(struct ieee80211_tx_info * info);

ARGUMENTS

       info
	   The struct ieee80211_tx_info to be cleared.

DESCRIPTION

       When the driver passes an skb back to mac80211, it must report a number of things in TX status. This function clears everything in the TX
       status but the rate control information (it does clear the count since you need to fill that in anyway).

NOTE

       You can only use this function if you do NOT use info->driver_data! Use info->rate_driver_data instead if you need only the less space that
       allows.

AUTHOR

       Johannes Berg <johannes@sipsolutions.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   IEEE80211_TX_INFO_CL(9)

STRUCT 
IEEE80211_TX_(9) 				  The basic mac80211 driver inte				   STRUCT IEEE80211_TX_(9)

NAME

       struct_ieee80211_tx_rate - rate selection/status

SYNOPSIS

       struct ieee80211_tx_rate {
	 s8 idx;
	 u16 count:5;
	 u16 flags:11;
       };

MEMBERS

       idx
	   rate index to attempt to send with

       count
	   number of tries in this rate before going to the next rate

       flags
	   rate control flags (enum mac80211_rate_control_flags)

DESCRIPTION

       A value of -1 for idx indicates an invalid rate and, if used in an array of retry rates, that no more rates should be tried.

       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.

AUTHOR

       Johannes Berg <johannes@sipsolutions.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   STRUCT IEEE80211_TX_(9)