From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from s72.web-hosting.com (s72.web-hosting.com [198.187.29.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 957CE21F204 for ; Sun, 19 Jan 2014 19:33:01 -0800 (PST) Received: from [117.199.143.19] (port=57367 helo=nako) by server72.web-hosting.com with esmtpsa (UNKNOWN:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1W55bc-002PF4-Pn; Sun, 19 Jan 2014 22:32:57 -0500 From: Sujith Manoharan MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <21212.38828.910370.71395@gargle.gargle.HOWL> Date: Mon, 20 Jan 2014 08:57:40 +0530 To: Dave Taht In-Reply-To: References: X-Mailer: VM 8.2.0b under 24.3.50.1 (x86_64-unknown-linux-gnu) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server72.web-hosting.com X-AntiAbuse: Original Domain - lists.bufferbloat.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - msujith.org X-Get-Message-Sender-Via: server72.web-hosting.com: authenticated_id: sujith@msujith.org X-Source: X-Source-Args: X-Source-Dir: Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] looking over ampdu stats X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jan 2014 03:33:08 -0000 Dave Taht wrote: > in my tests, we almost never see more than 2 AMPDUs stacked up. (just > running netperf, not rrul). 2 is the minimum queue depth to aggregate packets. From ath9k.h: #define ATH_AGGR_MIN_QDEPTH 2 > This could be the fault of the client device I'm using... This is not a bug with the client. > cat /sys/kernel/debug/ieee80211/phy1/ath9k/queues > > (note: have set the default be_qlen to the default here) > > (VO): qnum: 0 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0 > (VI): qnum: 1 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0 > (BE): qnum: 2 qdepth: 3 ampdu-depth: 2 pending: 60 stopped: 0 > (BK): qnum: 3 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0 > (CAB): qnum: 8 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0 qlen will not affect the minimum aggregate threshold, so adjusting be_qlen will not affect aggregation. Sujith