From: "John W. Linville" <linville@tuxdriver.com>
To: Adrian Bassett <adrian.bassett@hotmail.co.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rtl8180 Bit Rate regression in 2.6.29
Date: Mon, 16 Mar 2009 14:08:32 -0400 [thread overview]
Message-ID: <20090316180832.GC3660@tuxdriver.com> (raw)
In-Reply-To: <COL113-W348B209977311F6BB460ADCB9B0@phx.gbl>
On Mon, Mar 16, 2009 at 12:22:50PM +0000, Adrian Bassett wrote:
>
>
> (I'm not currently subscribed so please Cc: in any response ...)
>
> Using PCI device 1799:700f and the rtl8180 kernel wireless driver.
>
> With the vanilla 2.6.29-rc releases (rc8 most recently but also with predecessors) I've noticed that the Bit Rate of my wireless device appears to be more or less fixed at 1 Mb/s. Occasionally, iwconfig reports higher values but, as the stats below show, no attempts are successful at higher Bit Rates with this kernel version.
>
> With the 2.6.28 series, however, the Bit Rate will vary in the normal way, with the majority of the network activity happening at the higher end, if not the highest(54 Mb /s) point, of the range supported by this device.
>
> This is using the minstrel rate control mechanism.
FWIW, are you sure? PID was still the default in 2.6.28 IIRC.
The "run to the highest available rate" behavior was typical of PID.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-03-16 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 12:22 rtl8180 Bit Rate regression in 2.6.29 Adrian Bassett
2009-03-16 14:40 ` Larry Finger
2009-03-16 15:04 ` Adrian Bassett
2009-03-16 15:06 ` Hin-Tak Leung
2009-03-16 18:08 ` John W. Linville [this message]
2009-03-16 20:25 ` FW: " Adrian Bassett
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 19:06 RTL8180 Bit Rate Regression " Adrian Bassett
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=20090316180832.GC3660@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=adrian.bassett@hotmail.co.uk \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).