[ath9k-devel] Questions in 802.11 n timestamps traces for aggregated frames ?

[Felix Fietkau <nbd@openwrt.org>]

On 2013-03-16 9:19 PM, abhinav narain wrote:
> 
>     > guess aggr of 1462 bytes ?),
>     > but why are those seq. numbers never re-used ?
>     Your traces don't give you the full picture, because looking at this as
>     a per-frame thing is wrong.
>     If both IEEE80211_TX_CTL_AMPDU and IEEE80211_TX_STAT_AMPDU are set, it
>     means that the contained rate retry information and time stamp refer to
>     the whole A-MPDU, not just that one frame. Information about software
>     retry of frames is not passed on to mac80211 at the moment.
>     If you want accurate timestamp, rate and retry information, do it per
>     A-MPDU, not per MPDU.
> 
> Hi Felix, 
> I think I have understood you correctly, but let me know if I have got
> you wrong.
> 
> 
> 
> *594 *is the*first* frame of the aggregate and the *rate* information
> from its descriptor has to be used *for the whole aggregate frame* 594-603.
> Since the frames *595-603* seq. no. have the flag IEEE80211_TX_CTL_AMPDU
> set and flag  IEEE80211_TX_STAT_AMPDU not set, they are a part of the
> AMPDU starting at 594 and all the rate/retx information is ignored.
That's correct.

- Felix