Message-ID: <4F20039C.2030809@01019freenet.de> (sfid-20120125_143132_856571_463F873A)
Date: Wed, 25 Jan 2012 14:29:00 +0100
From: Andreas Hartmann <andihartmann@01019freenet.de>
MIME-Version: 1.0
To: Helmut Schaa <helmut.schaa@googlemail.com>
CC: linux-wireless@vger.kernel.org
Subject: Re: ath9k get's completely knocked out by rt3572 device
References: <4F1EF618.6080108@01019freenet.de> <13411135.eH6opTgxBo@helmutmobil.site> <4F1FBA09.3000003@01019freenet.de> <4F1FDEAE.2020009@01019freenet.de> <CAGXE3d9Lrk+ginqqbxVM+v_+fpnhu=y_R=TGdyoy+ZWuLtfbtQ@mail.gmail.com>
In-Reply-To: <CAGXE3d9Lrk+ginqqbxVM+v_+fpnhu=y_R=TGdyoy+ZWuLtfbtQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-wireless-owner@vger.kernel.org

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