From owner-freebsd-wireless@FreeBSD.ORG Tue Sep 13 14:46:09 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9C77106566B for ; Tue, 13 Sep 2011 14:46:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id A1E018FC0C for ; Tue, 13 Sep 2011 14:46:09 +0000 (UTC) Received: by gyf2 with SMTP id 2so619534gyf.13 for ; Tue, 13 Sep 2011 07:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=gIYGfZ/hvdk/1YlTGzol9fYE7izxjVabehWOwZB3bBk=; b=nfkunQHkUNyXlzG9VpiEWkQBMhCW+vIqojkKkBPsn2j70Js3KaCP14wy+DudbUbyt8 Fvo5sL3x27SnG6dxjvu3yzBsIyQMQVQe8rGHPOQn+NIE2BB2aBZVqKG+oX4lfgmzSAAY 1Cb1+WkUShfhKgELMyxpWPmR6Op9ujLqdRW4o= MIME-Version: 1.0 Received: by 10.236.185.195 with SMTP id u43mr33703936yhm.106.1315925168923; Tue, 13 Sep 2011 07:46:08 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.111.42 with HTTP; Tue, 13 Sep 2011 07:46:08 -0700 (PDT) In-Reply-To: References: Date: Tue, 13 Sep 2011 22:46:08 +0800 X-Google-Sender-Auth: nOlop_51iOuAfbLzL1vbbYoAbYg Message-ID: From: Adrian Chadd To: Berislav Purgar Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: [patch] if_ath_tx: change interrupt scheduling deferral X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2011 14:46:10 -0000 On 13 September 2011 18:14, Berislav Purgar wrote: > channel 6:ht/20 > > AR5416(iperf -c) ---> AR9280(iperf -s)=A0 i get TCP ~ 9MB/s=A0 UDP ~ 13MB= /s > AR9280(iperf -c) ---> AR5416(iperf -s) i=A0 get TCP ~ 4MB/s=A0 UDP ~ 8MB/= s Hm, 90/130 mbit; that's what it should be. But I wonder why it's so bad one= way. Time to do a bit of debugging. > channel 6:ht/40 > > AR5416(iperf -c) ----> AR9280(iperf -s) i get TCP ~ 7MB/s UDP ~ 10MB/s > AR9280(ipef -c) ----> AR5416(iperf -s) i get TCP ~ 15MB/s UDP ~ 24MB/s Nice. :) > after testing it in both direction i look at log files and found these er= ror > on AR5416 side > > Sep 13 11:54:25 rut kernel: ath0: device timeout > Sep 13 11:54:25 rut kernel: ath0: ath_tx_tid_drain: node 0xc421e000: tid = 0: > txq_ > depth=3D0, txq_aggr_depth=3D0, sched=3D1, paused=3D1, hwq_depth=3D0, inco= mp=3D0, > baw_head=3D0, > =A0baw_tail=3D0 txa_start=3D395, ni_txseqs=3D5266 > Sep 13 11:54:30 rut kernel: ath0: device timeout > Sep 13 11:54:30 rut kernel: ath0: ath_tx_tid_drain: node 0xc421e000: tid = 0: > txq_ > depth=3D0, txq_aggr_depth=3D0, sched=3D1, paused=3D1, hwq_depth=3D0, inco= mp=3D0, > baw_head=3D0, > =A0baw_tail=3D0 txa_start=3D51382, ni_txseqs=3D51383 > > > and on AR9280 > > Sep 13 11:55:34 pila kernel: ath2: device timeout > Sep 13 11:55:34 pila kernel: ath2: ath_tx_tid_drain: node 0xc3065000: tid= 0: > txq > _depth=3D0, txq_aggr_depth=3D0, sched=3D1, paused=3D1, hwq_depth=3D0, inc= omp=3D0, > baw_head=3D0 > , baw_tail=3D0 txa_start=3D2826, ni_txseqs=3D4496 > Sep 13 11:55:39 pila kernel: ath2: device timeout > Sep 13 11:55:39 pila kernel: ath2: ath_tx_tid_drain: node 0xc3065000: tid= 0: > txq > _depth=3D0, txq_aggr_depth=3D0, sched=3D1, paused=3D1, hwq_depth=3D0, inc= omp=3D0, > baw_head=3D0 > , baw_tail=3D0 txa_start=3D42270, ni_txseqs=3D42271 There shouldn't be errors on the AR5416, unless that chip also has the errant behaviour. I know the AR9280. Are you able to try the previous svn revision (from a couple days ago) and see if they have errors? I think I now know what the problem is, I'll work on trying to fix it. Also, paused=3D1 is a bit odd. I'll have to do some digging. The good news is that I do have an AR5416/AR9280 combination to test with. I'll just have to whack the AR5416 in a hostap mips board. Adrian