From: Andi Kleen <andi@firstfloor.org>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Andi Kleen <andi@firstfloor.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
Michael Buesch <mb@bu3sch.de>,
linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>
Subject: Re: rate instability in wireless stack
Date: Mon, 5 Jan 2009 16:24:10 +0100 [thread overview]
Message-ID: <20090105152410.GT496@one.firstfloor.org> (raw)
In-Reply-To: <49621C36.70602@openwrt.org>
On Mon, Jan 05, 2009 at 03:41:58PM +0100, Felix Fietkau wrote:
> Andi Kleen wrote:
> > With Larry's patch reverted. Rate is still at 1Mbit/s of course.
> > This is all only with rtl8180, I didn't try everything on the realtek
> > card too.
> >
> > -Andi
> >
> > rate throughput ewma prob this prob this succ/attempt success attempts
> > TtP 1 0.9 99.2 100.0 1( 1) 23 32
> > 2 0.0 0.0 0.0 0( 0) 0 0
> > 5.5 0.0 0.0 0.0 0( 0) 0 1
> > 11 0.0 0.0 0.0 0( 0) 0 0
> > 6 0.0 0.0 0.0 0( 0) 0 0
> > 9 0.0 0.0 0.0 0( 0) 0 0
> > 12 0.0 0.0 0.0 0( 0) 0 0
> > 18 0.0 0.0 0.0 0( 0) 0 0
> > 24 0.0 0.0 0.0 0( 0) 0 0
> > 36 0.0 0.0 0.0 0( 0) 0 0
> > 48 0.0 0.0 0.0 0( 0) 0 0
> > 54 0.0 0.0 0.0 0( 0) 0 0
> >
> > Total packet count:: ideal 25 lookaround 1
> OK, that confirms that Larry's patch was wrong - at least the dump
> looks consistent now.
> Probably the RT2561 and the RTL8180 simply have a lower Tx power and
> thus can't get the signal through the walls as easily as the zd1211rw.
That surprises me because I use a real antenna on them which the zd1211rw
is just itself. Also some laptops with Intel wireless have no trouble
talking through the walls at full rate when I put them on the same position.
Hmm perhaps I should try to find a Windows box and see if it works
there. That would rule out hardware issues.
> If you still think that it's a rate control problem, please try all
I don't know what it is, i just know that it doesn't work and
from the evidence I gathered so far it looks like a Linux software
problem.
> the rates individually and see if one of them works better.
Forcing the rates works somewhat, but the link quality is very poor
(10-15/100) and fluctuates.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2009-01-05 15:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 16:46 rate instability in wireless stack Andi Kleen
2009-01-04 16:36 ` Michael Buesch
2009-01-04 17:41 ` Andi Kleen
2009-01-05 0:29 ` Larry Finger
2009-01-05 2:53 ` Andi Kleen
2009-01-05 3:55 ` Larry Finger
2009-01-05 5:02 ` Andi Kleen
2009-01-05 4:59 ` Larry Finger
2009-01-05 5:48 ` Andi Kleen
2009-01-05 5:51 ` Larry Finger
2009-01-05 8:17 ` Johannes Berg
2009-01-05 12:54 ` Andi Kleen
2009-01-05 13:32 ` Felix Fietkau
2009-01-05 14:23 ` Andi Kleen
2009-01-05 14:41 ` Felix Fietkau
2009-01-05 15:24 ` Andi Kleen [this message]
2009-01-05 15:25 ` Felix Fietkau
2009-01-05 16:35 ` Andi Kleen
2009-01-05 16:36 ` Felix Fietkau
2009-01-05 17:11 ` Andi Kleen
2009-01-05 17:01 ` Felix Fietkau
2009-01-05 19:33 ` Hin-Tak Leung
2009-01-05 20:16 ` Larry Finger
2009-01-05 4:22 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 6:46 Martín Ernesto Barreyro
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=20090105152410.GT496@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=nbd@openwrt.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).