From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ath9k get's completely knocked out by rt3572 device
Date: Wed, 25 Jan 2012 14:29:00 +0100 [thread overview]
Message-ID: <4F20039C.2030809@01019freenet.de> (raw)
In-Reply-To: <CAGXE3d9Lrk+ginqqbxVM+v_+fpnhu=y_R=TGdyoy+ZWuLtfbtQ@mail.gmail.com>
Helmut Schaa schrieb:
> On Wed, Jan 25, 2012 at 11:51 AM, Andreas Hartmann
> <andihartmann@01019freenet.de> wrote:
>> As promised, I repeated the test before with another AP. The
>> destination host of netperf was the same. See below!
>
> So, in total it looks a little bit better then with the rt2800pci AP
> but still the airtime is distributed not equally but the Ralink STA
> seems to get a higher amount of airtime :(.
Well, the amount of sent data from AP -> STA is much higher with rt2860
based AP. So, the density is higher as with the Linksys WAP. Could this
be a problem for ath9k? But ath9k runs very well, if the conditions are
better (not as much disruption).
The rt2860 based AP feels smoother than the Linksys WAP. If the reverse
way could be optimized, it would be a great AP :-).
But you have to take into consideration, that the rt2860 AP resides
directly on PCI and isn't restricted to fast ethernet. The throughput
peaks with the rt2860 based AP where about 14 MBit/s (-> xosview). These
couldn't be seen with the Linksys WAP.
>
> Maybe the ralink driver treats the channel access parameters
> differently?
Don't know.
Andreas
prev parent reply other threads:[~2012-01-25 13:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 18:19 ath9k get's completely knocked out by rt3572 device Andreas Hartmann
2012-01-24 20:07 ` Helmut Schaa
2012-01-24 21:52 ` Andreas Hartmann
2012-01-25 7:53 ` Helmut Schaa
2012-01-25 8:15 ` Andreas Hartmann
2012-01-25 10:51 ` Andreas Hartmann
2012-01-25 12:23 ` Helmut Schaa
2012-01-25 13:29 ` Andreas Hartmann [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=4F20039C.2030809@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=helmut.schaa@googlemail.com \
--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).