On 2013-02-25 9:53 PM, abhinav narain wrote: > You are right in that case, Adrian. > > *tsf ,retx count, rates and transmit attempts, sequence no, frame size* > *[315063930, 14,[[65.0, 4], [58.5, 5], [65.0, 5]], 706,1542]* > *[315063930, 14,[[65.0, 4], [58.5, 5], [65.0, 5]], 707,1542]* > *[315063930, 14,[[65.0, 4], [58.5, 5], [65.0, 5]], 708,1542]* > *[315063930, 14,[[65.0, 4], [58.5, 5], [65.0, 5]], 709,1542]* > > I have the above trace of transmitted frames from status.c file. > You can see the frame sequence no. is increasing 706,707 ... > but the timestamps are all the same. > Apart from it, every frame is suffering retransmissions. > > I had found the timestamp value using ath_tx_status descriptor's > ts_tstamp field in > ath_tx_complete_buf() in xmit.c > > Since ath_tx_status is per frame and hence its time field, how is it > that the timestamp is not unique. > > Can you guess whats going wrong, by any chance ? With aggregation, you get a single tx status for a whole aggregate.
- Felix _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
