From mboxrd@z Thu Jan 1 00:00:00 1970 From: Felix Fietkau Date: Mon, 25 Feb 2013 22:01:35 +0100 Subject: [ath9k-devel] ts_tstamp field in ath_tx_status is set In-Reply-To: References: Message-ID: <512BD12F.1030003@openwrt.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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