Hi Yeoh, Thanks for taking the time to re-test this. You nailed it:
> By the way, are you using the ath9k_htc, mwl8k, or TI drivers? Yes :(, ath9k_htc. Thanks! Javier On Sun, Jul 1, 2012 at 7:18 PM, Yeoh Chun-Yeow <[email protected]> wrote: > Hi, Javier > > I have confirmed that both rate control algorithms are working for > multicast. Here is the iperf performance. > > bin/iperf.exe -s -u -P 0 -i 1 -p 5001 -B 225.0.0.1 -f m > ------------------------------------------------------------ > Server listening on UDP port 5001 > Binding to local address 192.168.1.10 > Receiving 1470 byte datagrams > UDP buffer size: 0.01 MByte (default) > ------------------------------------------------------------ > [1864] local 192.168.1.10 port 5001 connected with 192.168.1.3 port 64510 > [ ID] Interval Transfer Bandwidth Jitter Lost/Total > Datagrams > [1864] 0.0- 1.0 sec 1.69 MBytes 14.2 Mbits/sec 1.177 ms > 1886414875/ 1883 (1e+008%) > [1864] 1.0- 2.0 sec 1.72 MBytes 14.5 Mbits/sec 1.485 ms 902/ 2131 (42%) > [1864] 2.0- 3.0 sec 1.61 MBytes 13.5 Mbits/sec 1.203 ms 1037/ 2184 (47%) > [1864] 3.0- 4.0 sec 1.65 MBytes 13.9 Mbits/sec 0.763 ms 963/ 2143 (45%) > [1864] 4.0- 5.0 sec 1.66 MBytes 13.9 Mbits/sec 0.568 ms 993/ 2178 (46%) > [1864] 5.0- 6.0 sec 1.69 MBytes 14.2 Mbits/sec 0.867 ms 974/ 2180 (45%) > [1864] 6.0- 7.0 sec 1.64 MBytes 13.7 Mbits/sec 0.305 ms 1008/ 2175 (46%) > [1864] 7.0- 8.0 sec 1.64 MBytes 13.7 Mbits/sec 0.788 ms 1028/ 2197 (47%) > [1864] 8.0- 9.0 sec 1.63 MBytes 13.7 Mbits/sec 0.533 ms 995/ 2158 (46%) > [1864] 9.0-10.0 sec 1.64 MBytes 13.7 Mbits/sec 0.881 ms 1005/ 2174 (46%) > [1864] 0.0-10.1 sec 16.7 MBytes 13.8 Mbits/sec 1.420 ms 9708/21591 (45%) > > I am able to get 14Mbps if configure the 54Mbps multicast rate for the > established link. > > By the way, are you using the ath9k_htc, mwl8k, or TI drivers? It > seems that those drivers have hardware rate control mechanisms. > > The HW flag "IEEE80211_HW_HAS_RATE_CONTROL" in those drivers has > disabled the rate control algorithm in mac80211. Refer to tx.c: > > if (!(tx->local->hw.flags & IEEE80211_HW_HAS_RATE_CONTROL)) > CALL_TXH(ieee80211_tx_h_rate_ctrl); > > Attached are wireshark capture pictures for the transmission rate used > for multicast frame and broadcast beacon frame. > > Thanks > > Regards, > Chun-Yeow > > On Sat, Jun 30, 2012 at 2:35 PM, Yeoh Chun-Yeow <[email protected]> > wrote: >> Hi, Javier >> >>> Sniffer confirms only 1 Mbps data rate is used. Diving through the >>> code the implements this, it appears that this is dependent on the >>> rate control. >> Last time, I observed on the sniffer that the broadcast management >> frame and multicast video streaming data are both switched to the >> configured mcast-rate. AFAIK, broadcast/multicast frame are >> transmitted without ACK from the receiver. So rate control is not >> applicable to multicast frame, shouldn't it? >> >>> What rate control algorithm did you test this setting on? >> Anyway, my default rate control algorithm are switched between >> Minstrel or ath9k rate control. Also let me further confirm back with >> mcast transmission rate again when I back to office. >> >> Thanks >> >> Regards, >> Chun-Yeow -- Javier Cardona cozybit Inc. http://www.cozybit.com _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
