From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= Date: Tue, 10 May 2016 09:14:14 -0000 Subject: [ath9k-devel] [Make-wifi-fast] Diagram of the ath9k TX path In-Reply-To: (David Lang's message of "Mon, 9 May 2016 22:22:22 -0700 (PDT)") References: <871t5bpkc7.fsf@toke.dk> <6ADC1A9D-72C9-47A5-BDC7-94C14ED34379@gmail.com> Message-ID: <87vb2mmgg5.fsf@toke.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org David Lang writes: > There are two parts to this process > > 1. the tactical (do you send the pending packet immediately, or do you > delay it to see if you can save airtime with aggregation) A colleague of mine looked into this some time ago as part of his PhD thesis. This was pre-801.11n, so they were doing experiments on adding aggregation to 802.11g by messing with the MTU. What they found was that they actually got better results from just sending data when they had it rather than waiting to see if more showed up. -Toke