Linux wireless drivers development
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Abhijeet Kolekar <abhijeet.kolekar@intel.com>
Cc: "Chatre, Reinette" <reinette.chatre@intel.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ipw3945-devel@lists.sourceforge.net"
	<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [ipw3945-devel] [PATCH 3/8] iwl3945 : fix rate scaling
Date: Fri, 13 Mar 2009 01:56:58 +0200	[thread overview]
Message-ID: <1236902218.13039.8.camel@maxim-laptop> (raw)
In-Reply-To: <1236897665.3911.8.camel@abhi-desktop>

On Thu, 2009-03-12 at 15:41 -0700, Abhijeet Kolekar wrote:
> Can you try the attached patch for rate scaling?

Just tried it.
It doesn't make things worse, but nether better.

It seems that I can fully control speeds using iwconfig, and when speed
drop, I see that there.

Now speed dropped to 48 Mbits/s raw or 2.9 Mbytes/s real upload.
But I can reset it to 54Mbits/s, then set speed to auto, then it will be
3.1 for a while, then drops again.

On the other hand speed is quite stable, it drops once in a while due to
scanning for few seconds to about 2.2 Mbytes/s, then restores itself
again.

This was more or less the same as without this patch (I also use hw
scanning now).


Anyway, it is almost perfect. All I need to do it to set speed to
54Mbits/s manually.

Best regards and thanks,
	Maxim Levitsky


  reply	other threads:[~2009-03-12 23:57 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       ` [ipw3945-devel] [PATCH 3/8] iwl3945 : fix rate scaling Maxim Levitsky
2009-03-12  2:29         ` 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 [this message]
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=1236902218.13039.8.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=abhijeet.kolekar@intel.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