struct_rate_info(9) [centos man page]

STRUCT 
RATE_INFO(9)					     Actions and configuration					       STRUCT RATE_INFO(9)

NAME

       struct_rate_info - bitrate information

SYNOPSIS

       struct rate_info {
	 u8 flags;
	 u8 mcs;
	 u16 legacy;
	 u8 nss;
       };

MEMBERS

       flags
	   bitflag of flags from enum rate_info_flags

       mcs
	   mcs index if struct describes a 802.11n bitrate

       legacy
	   bitrate in 100kbit/s for 802.11abg

       nss
	   number of streams (VHT only)

DESCRIPTION

       Information about a receiving or transmitting bitrate

AUTHOR

       Johannes Berg <johannes@sipsolutions.net>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						       STRUCT RATE_INFO(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)