Erm, there isn't anything in the attempted bitrate array. I have no idea how to interpret this and I have no idea when this stuff is being output.
The important thing to remember here is that if there's a whole-frame transmit failure (ie, the status isn't ok, there's some kind of xretry, filt, etc error) then the majority of the TX status descriptor may be invalid. So I suggest you print out the status and flags field from the TX completion status descriptor to completely understand what's going on here. Adrian On 10 March 2013 14:01, abhinav narain <abhinavnarai...@gmail.com> wrote: > Hi, > I have questions regarding 802.11n transmission behavior. > The last number tx flag array shows a frame aggregation in the driver > [0,0,0,1] in the trace below. > aggregation flag is set by using : bf->bf_state.bf_type & BUF_AGGR // xmit.c > > Seq no: 3705-3708 & 3717-3720 show the same retx,bitrates attempted and > hence look like an ampdu. > The mpdus with seq. number 3704, 3716 have the same transmission time but > different attempted bitrates. > > Which leads me to the following questions : > 1) How is 3704 is having a different attempted rate, when it is part of an > ampdu ? > (an ampdu must have one block ack, which will have same fate for all the > subframes) > > 2) Does the h/w give the time when frame is going to be transmitted ? > (ath_tx_status->ts_tstamp) > and not the time when its successfully transmitted/done with it. > > 3) 3704 looks more like mpdu (normal frame), and one normal frame is always > sent before an ampdu ( I have many such traces) > Is it a bug ? or could someone explain what does hadware actually does ? > > Station connected tsf, tx flags, retx, attempted birates, seq > number, queuing delay,dummy no,frame size > 64:a7:69:53:0b:15 290861410 [0, 0, 0, 1] 0 [] 3704 > 1870 2 152 > 64:a7:69:53:0b:15 290861410 [0, 0, 0, 1] 14 [[65.0, 4], [52.0, 5], [65.0, > 5]] 3705 3258 2 94 > 64:a7:69:53:0b:15 290861410 [0, 0, 0, 1] 14 [[65.0, 4], [52.0, 5], [65.0, > 5]] 3706 3380 2 1462 > 64:a7:69:53:0b:15 290861410 [0, 0, 0, 1] 14 [[65.0, 4], [52.0, 5], [65.0, > 5]] 3707 626 2 1462 > 64:a7:69:53:0b:15 290861410 [0, 0, 0, 1] 14 [[65.0, 4], [52.0, 5], [65.0, > 5]] 3708 2473 2 154 > 64:a7:69:53:0b:15 290870565 [0, 0, 0, 0] 0 [] 3709 952 2 94 > 64:a7:69:53:0b:15 290871089 [0, 0, 0, 0] 0 [] 3710 2771 2 531 > 64:a7:69:53:0b:15 290879639 [0, 0, 0, 0] 0 [] 3711 998 2 308 > 64:a7:69:53:0b:15 290977852 [0, 0, 0, 0] 1 [[65.0, 1]] 3712 360 2 102 > 64:a7:69:53:0b:15 291010441 [0, 0, 0, 0] 0 [] 3713 199 2 94 > 64:a7:69:53:0b:15 291012659 [0, 0, 0, 0] 0 [] 3714 483 2 1462 > 64:a7:69:53:0b:15 291013067 [0, 0, 0, 0] 0 [] 3715 2342 2 1462 > 64:a7:69:53:0b:15 291015057 [0, 0, 0, 1] 0 [] 3716 1902 2 1462 > 64:a7:69:53:0b:15 291015057 [0, 0, 0, 1] 14 [[65.0, 4], [52.0, 5], [65.0, > 5]] 3717 2372 2 1462 > 64:a7:69:53:0b:15 291015057 [0, 0, 0, 1] 14 [[65.0, 4], [52.0, 5], [65.0, > 5]] 3718 1859 2 1462 > 64:a7:69:53:0b:15 291015057 [0, 0, 0, 1] 14 [[65.0, 4], [52.0, 5], [65.0, > 5]] 3719 708 2 1462 > 64:a7:69:53:0b:15 291015057 [0, 0, 0, 1] 14 [[65.0, 4], [52.0, 5], [65.0, > 5]] 3720 2568 2 102 > > - > Abhinav > > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel > _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
