From: Larry Finger <Larry.Finger@lwfinger.net>
To: htl10@users.sourceforge.net
Cc: Herton Ronaldo Krzesinski <herton@mandriva.com.br>,
linux-wireless@vger.kernel.org,
John W Linville <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
Michael Wu <flamingice@sourmilk.net>,
Andrea Merello <andrea.merello@gmail.com>
Subject: Re: [RFC/RFT PATCH v2 2/2] rtl8187: feedback transmitted packets using tx close descriptor for 8187B
Date: Wed, 05 Nov 2008 16:18:09 -0800 [thread overview]
Message-ID: <491237C1.4090701@lwfinger.net> (raw)
In-Reply-To: <813803.32421.qm@web23102.mail.ird.yahoo.com>
Hin-Tak Leung wrote:
>
> Before installing compat-wireless, I think the rate started at 36Mb and moves up to 54Mb and get stuck at 54Mb as soon as any traffic is getting through; after installing the patched compat-wireless, the rate changes beteen 1Mb and 9Mb for a bit but get stuck at 1Mb as soon as any substantial traffic is getting through. I can manually switch it with "iwconfig wlan2 rate 36M", for example, but with an auto, "iwconfig wlan2 rate 36M auto", it drops back to 1Mb very soon.
>
> Baring changes in the rest of the wireless stack (which might come to the same thing), it is probably the changes surrounding status.rate[0].count vs status.retry_count which causes the 1Mb-rate-stuck...
>
> Did Larry get the v2 patches to do rate-control working (i.e. the rate actually changing with demand), or not? Larry's reply was "the rate-control mechanism works the way it did before" - I am not sure about the "it did" bit - same as v1 (rate stuck at 1Mb) or same as the prototype patch for 2.6.27 (rate changing with demand)?
On my system is started at 1 Mbs and rapidly moved to 54Mbs. It went so quickly
that by the time I started a ping, switched terminals, and issued an ivconfig,
it was already at 54 Mbs.
Larry
next prev parent reply other threads:[~2008-11-06 0:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 2:02 [RFC/RFT PATCH v2 2/2] rtl8187: feedback transmitted packets using tx close descriptor for 8187B Hin-Tak Leung
2008-11-05 15:42 ` Herton Ronaldo Krzesinski
2008-11-05 17:11 ` Hin-Tak Leung
2008-11-05 21:36 ` Herton Ronaldo Krzesinski
2008-11-05 22:05 ` Hin-Tak Leung
2008-11-05 22:43 ` Luis R. Rodriguez
2008-11-05 23:16 ` Hin-Tak Leung
2008-11-05 23:35 ` Luis R. Rodriguez
2008-11-06 14:14 ` John W. Linville
2008-11-06 18:53 ` Luis R. Rodriguez
2008-11-06 0:00 ` Hin-Tak Leung
2008-11-06 0:18 ` Larry Finger [this message]
2008-11-06 1:02 ` Hin-Tak Leung
2008-11-06 1:36 ` Hin-Tak Leung
2008-11-06 1:42 ` Larry Finger
2008-11-06 4:23 ` Hin-Tak Leung
2008-11-06 20:49 ` Hin-Tak Leung
-- strict thread matches above, loose matches on Subject: below --
2008-11-04 13:50 [RFC/RFT PATCH 0/2 v2] rtl8187: implement conf_tx callback/correctly ack tx pkts Herton Ronaldo Krzesinski
2008-11-04 13:50 ` [RFC/RFT PATCH v2 2/2] rtl8187: feedback transmitted packets using tx close descriptor for 8187B Herton Ronaldo Krzesinski
2008-11-04 20:27 ` Hin-Tak Leung
2008-11-04 21:30 ` Herton Ronaldo Krzesinski
2008-11-04 22:31 ` Larry Finger
2008-11-05 11:29 ` Johannes Berg
2008-11-05 15:38 ` Herton Ronaldo Krzesinski
2008-11-05 15:40 ` Johannes Berg
2008-11-05 15:59 ` Herton Ronaldo Krzesinski
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=491237C1.4090701@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=andrea.merello@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=herton@mandriva.com.br \
--cc=htl10@users.sourceforge.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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.