All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Cc: seno <senada@t-online.de>,
	linux-wireless@vger.kernel.org, hintak.leung@gmail.com
Subject: Re: [PATCH] rtl8187b: do not do per packet TX AGC
Date: Mon, 01 Nov 2010 11:24:41 -0500	[thread overview]
Message-ID: <4CCEE9C9.3090308@lwfinger.net> (raw)
In-Reply-To: <4CCE4479.1010400@mandriva.com.br>

On 10/31/2010 11:39 PM, Herton Ronaldo Krzesinski wrote:
> I have seen the throughput issue, but on my tests it wasn't so bad.
> Usually max I got on testing was 24M while close to the AP, and it goes
> into lower speeds when going more far away, but takes a good number of
> meters to go down to 1M.
> 
> Anyway of course something isn't right. I started reviewing realtek GPL
> code (their ieee80211 drivers) and code in rtl8187 in the kernel, doing
> many tests and verifying things, trying to understand and check some
> register writes etc. (hard with missing doc or other info).
> 
> I did some cleanups, and discovered two bad things in the code. After
> the fixes, I can get normal rates (up to 54M close to the AP) without
> issue. I'll soon post the patch series to be included in
> wireless-testing, for now just for test I attach them to be easier (hope
> it isn't stripped by ML, and yes they start on 0003 through 0011 :P),
> check if with it you get better results.
> 
> The patches that matter (shown by my tests) are:
> 0010-rtl8187-remove-uneeded-setting-of-anaparam-write.patch
> 0011-rtl8187-restore-anaparam-registers-after-reset-with-.patch
> 
> but they depend on some previous patches in the series (better apply
> all), and I diffed on a tree with Thadeu's patch applied already. There
> is more cleanups and checking to do, but I probably will submit this
> initial series and later come with more ones, as with this initial
> series the throughput issue should be solved.

Good work. As you noted, patches 3 - 9 did not make any difference in the
transmit throughput. From a distance of 2 m from the AP, my 8187B yielded up to
11.4 Mb/s and an indicated rate of 24 M. Applying patch 10 raised those numbers
to 17.5 Mb/s and 48 M. Adding patch 11 raised them again to 26.9 Mb/s and 54 M,
thus getting full throughput for the 8187B and a transmit rate increase of 2.4X.

As expected, these changes had no affect on the RTL8187L. Note: The 8187L gets
values of 23.0 Mb/s and 54M - there may be a little performance gain to be
obtained from the driver.

You should submit these patches now, and feel free to add my "Acked-by:" to them.

Larry

  reply	other threads:[~2010-11-01 16:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28  5:54 [PATCH] rtl8187b: do not do per packet TX AGC Thadeu Lima de Souza Cascardo
2010-08-28 21:32 ` Larry Finger
2010-08-30 14:12   ` John W. Linville
2010-08-30 14:48     ` Larry Finger
2010-08-30 15:28       ` Thadeu Lima de Souza Cascardo
2010-10-26 18:03         ` seno
2010-10-26 18:25           ` [PATCH] " Larry Finger
2010-10-26 18:53             ` Thadeu Lima de Souza Cascardo
2010-10-28 21:13               ` Herton Ronaldo Krzesinski
2010-10-28 22:01                 ` Thadeu Lima de Souza Cascardo
2010-10-29 13:15                   ` Herton Ronaldo Krzesinski
2010-10-28 23:21                 ` seno
2010-10-29 13:54                   ` Thadeu Lima de Souza Cascardo
2010-10-29 22:31                     ` seno
2010-10-30  0:00                       ` Larry Finger
2010-10-30  2:12                         ` seno
2010-11-01  4:39                       ` Herton Ronaldo Krzesinski
2010-11-01 16:24                         ` Larry Finger [this message]
2010-11-03  3:16                           ` Rogerio Luz Coelho
2010-11-04 14:23                           ` Hin-Tak Leung
2010-08-30 15:12   ` Thadeu Lima de Souza Cascardo
2010-09-16 18:44     ` John W. Linville

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=4CCEE9C9.3090308@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=herton@mandriva.com.br \
    --cc=hintak.leung@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=senada@t-online.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.