Linux wireless drivers development
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] [PATCH 3/8] iwl3945 : fix rate scaling
Date: Thu, 12 Mar 2009 03:29:20 +0200	[thread overview]
Message-ID: <1236821360.9581.78.camel@maxim-laptop> (raw)
In-Reply-To: <1236795481-12757-4-git-send-email-reinette.chatre@intel.com>

On Wed, 2009-03-11 at 11:17 -0700, Reinette Chatre wrote:
> From: Abhijeet Kolekar <abhijeet.kolekar@intel.com>
> 
> Patch fixes the bug 1900 at
> http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1900
> 
> Issues:
> Throughput and success ratio calculations were not done properly.
> Number of retries were exceeding 16.

At last... 

Here goes last annoying bug, inside my 
"Intel Corporation PRO/Wireless 3945ABG"

>From now on my wifi is perfect!


Well, that is what I thought, but although this patch helps a lot,
still some issues remain:


When I use disable_hw_scan=1, rate control issues still pop up.

This what happens to upload speed (tested using netcat, sending
a /dev/zero contents around:

For a while, it's solid at 3.0 Mbytes/s, a speed I would expect, but
then after a few minutes have passed, it drops down to about 2.8
Mbytes/s. Then again after few minutes it drops to 2.6 Mbytes/s, and
this pattern repeats. I waited till it hit 2.2 Mbytes/s.

Running iwconfig, reveals that this wifi card did run in 24Mbits/s mode
at that time! And trying force it to run in 54M/s mode didn't help
ether.

On the other omitting  the 'disable_hw_scan=1' option (which appears to
work once again, since  few days ago it broke s2disk with hung scan) -
rate didn't drop - it seemed to be always 
3.0/3.1(!) Mbytes/s, but after several minutes it did drop to
2.4Mbytes/s, and iwconfig showed the 36 Mbytes/s.
I set rate manually to 54Mbytes/s, and 3.0/3.1 rate returned.

So this helps, but something is still broken in rate control.



Downloads speeds, which I didn't test with hardware scanning disabled,
are, and I think always were at 2.4/2.5 Mbytes/s - and no more speed
drops ether it seems. Do you have a clue, why they are lower?
Also I noticed that for few seconds (about 15) download rate went as
high as 2.7 Mbytes/s.


In  addition to that, I glad to see , finally that functions were
merged, since they really need some love. For example, led appear to
blink at same rate regardless of transmit rate, be it a ssh session or a
torture speed test like I explained above. It seems that for few seconds
led blinks faster, but then reverts back to standard (minimal?) rate of
blinking.

Now at least it is worth to fix all that (when I have free time I do so,
that is if there will be need to do so....)


Best regards and thanks,
	Maxim Levitsky


  parent reply	other threads:[~2009-03-12  1:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 18:17 [PATCH 0/8] iwlwifi driver updates 03/11/2009 Reinette Chatre
2009-03-11 18:17 ` [PATCH 1/8] iwl3945: fix sparse error Reinette Chatre
2009-03-11 18:17   ` [PATCH 2/8] iwl3945: use iwl_led structure Reinette Chatre
2009-03-11 18:17     ` [PATCH 3/8] iwl3945 : fix rate scaling Reinette Chatre
2009-03-11 18:17       ` [PATCH 4/8] iwl3945: use iwl_tx_cmd_complete Reinette Chatre
2009-03-11 18:17         ` [PATCH 5/8] iwl3945: unmap previously mapped memory Reinette Chatre
2009-03-11 18:17           ` [PATCH 6/8] iwlagn: fix warning when set WEP key Reinette Chatre
2009-03-11 18:18             ` [PATCH 7/8] iwlwifi: print contents of control register when error occurs Reinette Chatre
2009-03-11 18:18               ` [PATCH 8/8] iwlwifi: correct log level " Reinette Chatre
2009-03-12  1:29       ` Maxim Levitsky [this message]
2009-03-12  2:29         ` [ipw3945-devel] [PATCH 3/8] iwl3945 : fix rate scaling Maxim Levitsky
2009-03-12 17:50           ` reinette chatre
2009-03-12 21:21             ` Maxim Levitsky
2009-03-12 21:58               ` Helmut Schaa
2009-03-12 22:03                 ` Maxim Levitsky
2009-03-12 23:58                   ` Maxim Levitsky
2009-03-13  6:28                     ` Helmut Schaa
2009-03-12 22:41               ` Abhijeet Kolekar
2009-03-12 23:56                 ` Maxim Levitsky
2009-03-13  0:18                   ` Maxim Levitsky
2009-03-13 20:29   ` [PATCH 1/8] iwl3945: fix sparse error Kalle Valo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1236821360.9581.78.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox