Message-ID: <4F1F2837.5090307@maya.org> (sfid-20120124_225624_236872_01C564FD)
Date: Tue, 24 Jan 2012 22:52:55 +0100
From: Andreas Hartmann <andihartmann@freenet.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>
In-Reply-To: <13411135.eH6opTgxBo@helmutmobil.site>
Content-Type: text/plain; charset=ISO-8859-15
Sender: linux-wireless-owner@vger.kernel.org

Helmut Schaa schrieb:
> Am Dienstag, 24. Januar 2012, 19:19:04 schrieb Andreas Hartmann:
>> - At the moment of stopping netperf on rt3572, the ath9k device
>> instantly started sending / receiving data again as expected.
> [...]
>> Does anybody has an idea what could cause this situation? Or is this normal?
> 
> Your netperf traffic is in the direction STA -> AP or also in the other
> direction?

In both directions (serially). It's a script, which does the following:

while true
do
	netperf -H host -t TCP_STREAM 	 # (STA -> AP)
	netperf -H host -t TCP_MAERTS    # (AP -> STA)
	netperf -H host -t TCP_SENDFILE  # (STA -> AP)
done


Andreas