From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ruwaifa Anwar <ruwaifa.anwar@gmail.com>
Date: Wed, 22 Jan 2014 16:35:35 +0000 (UTC)
Subject: [ath9k-devel] How to lock AMPDU length at a specific value?
References: <6112162.1390367992347.JavaMail.root@mail.ynu.ac.kr>
	<CADxDmp4rbg3DHnxYcEi2U+ru0bQ7mFs7BvDoPberbvP15ht1Kg@mail.gmail.com>
	<52DFE8FB.5030000@mailservices.uwaterloo.ca>
	<CADxDmp6+tNZoTmFU91UaXHp2zRj4zOZZ1AHLasHK8ucbd2+Stw@mail.gmail.com>
Message-ID: <loom.20140122T173052-536@post.gmane.org>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

yup, block-ack window limit appears to be the main culprit behind your 
reduced 
ampdu lengths. Check ath_tx_form_aggr, there is an if-condition specifically 
checking whether your are exceeding block-ack window or not. If your sending 
rate is quite high then increased lossess might trigger this condition quite 
frequently