linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: 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, 05 Jan 2009 16:25:58 +0100	[thread overview]
Message-ID: <49622686.9050005@openwrt.org> (raw)
In-Reply-To: <20090105152410.GT496@one.firstfloor.org>

Andi Kleen wrote:
>> 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.
Another possibility is that the tx power is fine, but the
sensitivity of the card is crap, so the packets actually make it,
but the ACKs don't. This is something that's quite hard to detect in
a rate control module that relies on ACKs as the only available
source of feedback (not that using RSSI for that would be any
better, but still).

Even if both cards work fine on Windows, I wouldn't assume that this
is an issue with mac80211. The information that was used to write
these two drivers was derived from very poor vendor codebases and
limited information in datasheets, so it's much more likely that
simply the Baseband/RF tuning is far from optimal on both cards.

Maybe we can see more if you provide some minstrel stats after
you've pushed more traffic through the link - 25-50 packets is not
nearly enough for getting an accurate view of how good the link is.
Try to push through a few megabytes of data...

- Felix

  reply	other threads:[~2009-01-05 15:26 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
2009-01-05 15:25                         ` Felix Fietkau [this message]
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=49622686.9050005@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=andi@firstfloor.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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).