From: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
To: "Hin-Tak Leung" <hintak_leung@yahoo.co.uk>
Cc: linux-wireless@vger.kernel.org, Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: throughput problem/bisect with rtl8187B
Date: Tue, 11 Nov 2008 11:10:26 -0200 [thread overview]
Message-ID: <200811111110.28066.herton@mandriva.com.br> (raw)
In-Reply-To: <41448.77528.qm@web23104.mail.ird.yahoo.com>
On Tuesday 11 November 2008 06:39:40 Hin-Tak Leung wrote:
> Hi Herton,
>
> I bisected through recent wireless-testing, and found the commit which results in my throughput problem - it is one of yours :-(. Can you and also possibly Larry give this a try: transfering some large files (>50MB) before and after reverting this particular commit, and see what sftp says about the transfer rate? You need to let sftp keep going for a while to see what rate it settles at. (>50MB should do, so a kernel source tarball
> would be appropriate). The difference is quite obvious in my case -
> <60kB/s, and 7x - 10x that if I revert this commit.
>
> The commit is all magic numbers, so if you see the problem, can you please
> have a look and check the numbers?
Lets try to identify what part is broken, I guess is this, can you try this
patch on latest wireless-testing?
diff --git a/drivers/net/wireless/rtl818x/rtl8187_dev.c b/drivers/net/wireless/rtl818x/rtl8187_dev.c
index d49f2a7..63c796e 100644
--- a/drivers/net/wireless/rtl818x/rtl8187_dev.c
+++ b/drivers/net/wireless/rtl818x/rtl8187_dev.c
@@ -913,7 +913,6 @@ static void rtl8187_conf_erp(struct rtl8187_priv *priv, bool use_short_slot,
{
if (priv->is_rtl8187b) {
u8 difs, eifs, slot_time;
- u16 ack_timeout;
if (use_short_slot) {
slot_time = 0x9;
@@ -933,19 +932,6 @@ static void rtl8187_conf_erp(struct rtl8187_priv *priv, bool use_short_slot,
* Value in units of 4 us
*/
rtl818x_iowrite8(priv, (u8 *)&priv->map->BRSR + 1, eifs);
-
- /*
- * For 8187B, CARRIER_SENSE_COUNTER is in fact ack timeout
- * register. In units of 4 us like eifs register
- * ack_timeout = ack duration + plcp + difs + preamble
- */
- ack_timeout = 112 + 48 + difs;
- if (use_short_preamble)
- ack_timeout += 72;
- else
- ack_timeout += 144;
- rtl818x_iowrite8(priv, &priv->map->CARRIER_SENSE_COUNTER,
- DIV_ROUND_UP(ack_timeout, 4));
} else {
rtl818x_iowrite8(priv, &priv->map->SIFS, 0x22);
if (use_short_slot) {
>
> Thanks,
> Hin-Tak
--
[]'s
Herton
next prev parent reply other threads:[~2008-11-11 13:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 6:01 throughput problem Re: [RFC/RFT PATCH v2 2/2] rtl8187: feedback transmitted packets using tx close descriptor for 8187B Hin-Tak Leung
2008-11-10 21:36 ` Herton Ronaldo Krzesinski
2008-11-10 21:55 ` Hin-Tak Leung
2008-11-11 8:39 ` throughput problem/bisect with rtl8187B Hin-Tak Leung
2008-11-11 13:10 ` Herton Ronaldo Krzesinski [this message]
2008-11-11 16:48 ` Hin-Tak Leung
2008-11-11 17:01 ` Larry Finger
2008-11-11 17:17 ` Hin-Tak Leung
2008-11-11 18:34 ` Herton Ronaldo Krzesinski
2008-11-11 19:42 ` Larry Finger
2008-11-12 1:12 ` Hin-Tak Leung
2008-11-12 19:10 ` Herton Ronaldo Krzesinski
2008-11-12 21:35 ` Larry Finger
2008-11-13 0:06 ` Hin-Tak Leung
2008-11-13 15:40 ` 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=200811111110.28066.herton@mandriva.com.br \
--to=herton@mandriva.com.br \
--cc=Larry.Finger@lwfinger.net \
--cc=hintak_leung@yahoo.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).