From: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
To: "Hin-Tak Leung" <hintak_leung@yahoo.co.uk>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: throughput problem/bisect with rtl8187B
Date: Thu, 13 Nov 2008 13:40:31 -0200 [thread overview]
Message-ID: <200811131340.32000.herton@mandriva.com.br> (raw)
In-Reply-To: <872129.29728.qm@web23105.mail.ird.yahoo.com>
On Wednesday 12 November 2008 22:06:16 Hin-Tak Leung wrote:
> --- On Wed, 12/11/08, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> > Herton Ronaldo Krzesinski wrote:
> > > Ok, Looks like sifs or eifs setting then expect values
> > in another format or
> > > have a different meaning may be (or just cause some hw
> > bug), it's strange,
> > > I suspect sifs value is the culprit. In the patch I
> > just reverted to values vendor
> > > driver uses, in it difs remains the same, just eifs
> > isn't changed for short slot
> > > case and kept with a default value (along with what is
> > supposed to be ack
> > > timeout register), and sifs set to 0x22. Please try
> > just the following change
> > > to isolate that the SIFS setting caused the throughput
> > issue:
> > >
> > > diff --git
> > a/drivers/net/wireless/rtl818x/rtl8187_dev.c
> > b/drivers/net/wireless/rtl818x/rtl8187_dev.c
> > > index d49f2a7..c0392e4 100644
> > > --- a/drivers/net/wireless/rtl818x/rtl8187_dev.c
> > > +++ b/drivers/net/wireless/rtl818x/rtl8187_dev.c
> > > @@ -924,7 +924,7 @@ static void
> > rtl8187_conf_erp(struct rtl8187_priv *priv, bool
> > use_short_slot,
> > > difs = 0x32;
> > > eifs = 0x5b;
> > > }
> > > - rtl818x_iowrite8(priv, &priv->map->SIFS,
> > 0xa);
> > > + rtl818x_iowrite8(priv, &priv->map->SIFS,
> > 0x22);
> > > rtl818x_iowrite8(priv, &priv->map->SLOT,
> > slot_time);
> > > rtl818x_iowrite8(priv, &priv->map->DIFS,
> > difs);
> >
> > This patch gives me the best performance yet. I get about
> > 1.0 MB/s download and
> > 580 KB/s upload with a 25 MB file using sftp.
>
> Yes, confirming this one number fixes the throughput problem I had. And I can also confirm that wireless-testing + this oneliner seems to be better than 2.6.27.
>
> I tried it alone on top of wireless-testing, and together with
> the conf_tx and feedback patches.
>
> Thanks for putting time into this!
nice, I sent the patch now plus the others pending I had.
>
> Hin-Tak
--
[]'s
Herton
prev parent reply other threads:[~2008-11-13 15:40 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
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 [this message]
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=200811131340.32000.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).