Thread: Re: [zd1211-devs] Rate configuration
Status: Beta
Brought to you by:
mayne
From: <j.c...@fr...> - 2009-12-10 10:33:37
|
> It should be fixed by : > http://git.popipo.fr/?p=rt2x00.git;a=commitdiff;h=eaad517e66173bf52dffd5157306fc39b66c4f5e > > commit eaad517e66173bf52dffd5157306fc39b66c4f5e > Author: Benoit PAPILLAULT <ben...@fr...> > Date: Thu Oct 22 12:04:52 2009 +0200 > > It's already in wireless-testing git tree, but apparently not in > 2.6.32 Isn't this patch already in bleeding edge compat-wireless ? I built the module from last week package and did not see any improvement. |
From: Benoit P. <ben...@fr...> - 2009-12-10 23:40:40
|
j.c...@fr... a écrit : >> It should be fixed by : >> http://git.popipo.fr/?p=rt2x00.git;a=commitdiff;h=eaad517e66173bf52dffd5157306fc39b66c4f5e >> >> commit eaad517e66173bf52dffd5157306fc39b66c4f5e >> Author: Benoit PAPILLAULT <ben...@fr...> >> Date: Thu Oct 22 12:04:52 2009 +0200 >> >> It's already in wireless-testing git tree, but apparently not in >> 2.6.32 > > Isn't this patch already in bleeding edge compat-wireless ? I built the module from last week package and did not see any improvement. > I don't know. You can check the source code this the patch is easy to identify. Regards, Benoit |
From: julien c. <j.c...@fr...> - 2009-12-14 12:43:26
|
Le lundi 14 décembre 2009 à 09:26 +0100, Benoit PAPILLAULT a écrit : > First, you need to run "iperf -s" on a server machine (not on your PC, best is a > machine on your wired LAN). Then, you need to run "iperf -c <server_IP>" on your > PC. It will connect to the iperf server and sends a TCP stream for 10 seconds. > After 10 seconds, it will display the throughput measured. A better command is : > "iperf -c <server_IP> -i 1 -t 60" => iperf will run for 60s instead of 10s and > will display throughput every seconds. I tried it between two of my computers, both on wireless, the client being the one using a zd1211rw chip. If i don't manually set the bitrate to 1M, I don't get any throughput. If I set it to 54M, I get * on the server side : [ 4] 0.0-11.6 sec 3.73 MBytes 2.70 Mbits/sec * on the client side : [ 3] 0.0-10.3 sec 3.73 MBytes 3.05 Mbits/sec But the rc_stats file still contains only zeroes : rate throughput ewma prob this prob this succ/attempt success attempts TtP 1 0.0 0.0 0.0 2( 0) 0 0 2 0.0 0.0 0.0 0( 0) 0 0 5.5 0.0 0.0 0.0 0( 0) 0 0 11 0.0 0.0 0.0 0( 0) 0 0 6 0.0 0.0 0.0 0( 0) 0 0 9 0.0 0.0 0.0 0( 0) 0 0 12 0.0 0.0 0.0 0( 0) 0 0 18 0.0 0.0 0.0 0( 0) 0 0 24 0.0 0.0 0.0 0( 0) 0 0 36 0.0 0.0 0.0 0( 0) 0 0 48 0.0 0.0 0.0 0( 0) 0 0 54 0.0 0.0 0.0 0( 0) 0 0 Total packet count:: ideal 2831 lookaround 149 Thanks for your help, Julien. |
From: Benoit P. <ben...@fr...> - 2009-12-14 23:56:41
|
julien cubizolles a écrit : > [cut] > I tried it between two of my computers, both on wireless, the client > being the one using a zd1211rw chip. > > If i don't manually set the bitrate to 1M, I don't get any throughput. > If I set it to 54M, I get > * on the server side : [ 4] 0.0-11.6 sec 3.73 MBytes 2.70 Mbits/sec > * on the client side : [ 3] 0.0-10.3 sec 3.73 MBytes 3.05 Mbits/sec > > But the rc_stats file still contains only zeroes : > OK. If you fixed the rate, then rate control is not used at all and this explain why rc_stats is full of zero! So, there is something really weird going on in your configuration that prevent rate control from working at all! Do you think you could narrow the problem by hacking into the source code? Regards, Benoit PS: If you are close to Paris, we can do a live debug session :-) |
From: <j.c...@fr...> - 2009-12-15 13:19:46
|
----- "Benoit PAPILLAULT" <ben...@fr...> a écrit : > So, there is something really weird going on in your configuration > that > prevent rate control from working at all! that's what I figured. > Do you think you could narrow the problem by hacking into the source > code? I've never done any driver hacking, I think It would take me days to debug. > Regards, > Benoit > PS: If you are close to Paris, we can do a live debug session :-) Je suis à Paris même, on peut faire ça effectivement. Julien. |
From: Benoit P. <ben...@fr...> - 2009-12-11 20:57:13
|
julien cubizolles a écrit : > Le vendredi 11 décembre 2009 à 00:13 +0100, Benoit PAPILLAULT a écrit : > > >> I don't know. You can check the source code this the patch is easy to >> identify. > > I checked. The patch is committed in compat-wireless bleeding edge but > doesn't seem to improve the problem I described. > > Julien. > > Please reply to the list as well, it's very annoying to bug me this way. In order to get more information on what happens in your situation, you need to use debugfs : mount -t debugfs debugfs /sys/kernel/debug Then, minstrel statistics should be available in : /sys/kernel/debug/ieee80211/phy<x>/stations/<mac>/rc_stats Please provide a copy of this file after doing an iperf over your wireless link for instance. Regards, Benoit |
From: julien c. <j.c...@fr...> - 2009-12-14 08:04:44
|
Le vendredi 11 décembre 2009 à 21:56 +0100, Benoit PAPILLAULT a écrit : > In order to get more information on what happens in your situation, you > need to use debugfs : > > mount -t debugfs debugfs /sys/kernel/debug > > Then, minstrel statistics should be available in : > > /sys/kernel/debug/ieee80211/phy<x>/stations/<mac>/rc_stats > > Please provide a copy of this file after doing an iperf over your > wireless link for instance. Could you tell me which iperf command to run ? I've never used it and maybe I'm doing something wrong but I tried : iperf -c 192.168.0.254 -m -w 200K -i 3 -t 30 -r -r and I only get : ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 256 KByte (WARNING: requested 200 KByte) ------------------------------------------------------------ and no measurements (192.168.0.254 is the name of my gateway). Here is the corresponding rc_stats file anyway but I guess it's of no use: rate throughput ewma prob this prob this succ/attempt success attempts TtP 1 0.0 0.0 0.0 1( 0) 0 0 2 0.0 0.0 0.0 0( 0) 0 0 5.5 0.0 0.0 0.0 0( 0) 0 0 11 0.0 0.0 0.0 0( 0) 0 0 6 0.0 0.0 0.0 0( 0) 0 0 9 0.0 0.0 0.0 0( 0) 0 0 12 0.0 0.0 0.0 0( 0) 0 0 18 0.0 0.0 0.0 0( 0) 0 0 24 0.0 0.0 0.0 0( 0) 0 0 36 0.0 0.0 0.0 0( 0) 0 0 48 0.0 0.0 0.0 0( 0) 0 0 54 0.0 0.0 0.0 0( 0) 0 0 Total packet count:: ideal 4858 lookaround 255 |
From: Benoit P. <ben...@fr...> - 2009-12-14 08:53:46
|
julien cubizolles a écrit : > Le vendredi 11 décembre 2009 à 21:56 +0100, Benoit PAPILLAULT a écrit : > >> In order to get more information on what happens in your situation, you >> need to use debugfs : >> >> mount -t debugfs debugfs /sys/kernel/debug >> >> Then, minstrel statistics should be available in : >> >> /sys/kernel/debug/ieee80211/phy<x>/stations/<mac>/rc_stats >> >> Please provide a copy of this file after doing an iperf over your >> wireless link for instance. > Could you tell me which iperf command to run ? I've never used it and > maybe I'm doing something wrong but I tried : > > iperf -c 192.168.0.254 -m -w 200K -i 3 -t 30 -r -r > > and I only get : > > ------------------------------------------------------------ > Server listening on TCP port 5001 > TCP window size: 256 KByte (WARNING: requested 200 KByte) > ------------------------------------------------------------ > > and no measurements (192.168.0.254 is the name of my gateway). First, you need to run "iperf -s" on a server machine (not on your PC, best is a machine on your wired LAN). Then, you need to run "iperf -c <server_IP>" on your PC. It will connect to the iperf server and sends a TCP stream for 10 seconds. After 10 seconds, it will display the throughput measured. A better command is : "iperf -c <server_IP> -i 1 -t 60" => iperf will run for 60s instead of 10s and will display throughput every seconds. > > Here is the corresponding rc_stats file anyway but I guess it's of no > use: > > rate throughput ewma prob this prob this succ/attempt success > attempts > TtP 1 0.0 0.0 0.0 1( 0) 0 > 0 > 2 0.0 0.0 0.0 0( 0) 0 > 0 > 5.5 0.0 0.0 0.0 0( 0) 0 > 0 > 11 0.0 0.0 0.0 0( 0) 0 > 0 > 6 0.0 0.0 0.0 0( 0) 0 > 0 > 9 0.0 0.0 0.0 0( 0) 0 > 0 > 12 0.0 0.0 0.0 0( 0) 0 > 0 > 18 0.0 0.0 0.0 0( 0) 0 > 0 > 24 0.0 0.0 0.0 0( 0) 0 > 0 > 36 0.0 0.0 0.0 0( 0) 0 > 0 > 48 0.0 0.0 0.0 0( 0) 0 > 0 > 54 0.0 0.0 0.0 0( 0) 0 > 0 > > Total packet count:: ideal 4858 lookaround 255 Your counters are zero, so it's not useful yet, run iperf or browse some web pages first. Regards, Benoit |