From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [Make-wifi-fast] Diagram of the ath9k TX path
Date: Tue, 10 May 2016 09:14:14 -0000 [thread overview]
Message-ID: <87vb2mmgg5.fsf@toke.dk> (raw)
In-Reply-To: <alpine.DEB.2.02.1605092200440.23321@nftneq.ynat.uz> (David Lang's message of "Mon, 9 May 2016 22:22:22 -0700 (PDT)")
David Lang <david@lang.hm> 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
next prev parent reply other threads:[~2016-05-10 9:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871t5bpkc7.fsf@toke.dk>
2016-05-09 15:35 ` [ath9k-devel] [Make-wifi-fast] Diagram of the ath9k TX path Dave Taht
2016-05-10 2:32 ` Jonathan Morton
2016-05-10 2:59 ` Dave Taht
2016-05-10 3:30 ` Adrian Chadd
2016-05-10 4:04 ` Dave Taht
2016-05-10 4:28 ` Aaron Wood
2016-05-10 7:15 ` Adrian Chadd
2016-05-10 7:17 ` Adrian Chadd
2016-05-10 3:49 ` David Lang
2016-05-10 4:59 ` Dave Taht
2016-05-10 5:22 ` David Lang
2016-05-10 9:14 ` Toke Høiland-Jørgensen [this message]
2016-05-13 17:52 ` Bob McMahon
2016-05-13 17:49 ` Dave Taht
2016-05-13 18:05 ` Bob McMahon
2016-05-13 18:11 ` Bob McMahon
2016-05-13 18:57 ` Dave Taht
2016-05-13 19:27 ` Aaron Wood
2016-05-13 20:21 ` Dave Taht
2016-05-13 20:51 ` Dave Taht
2016-05-13 20:49 ` David Lang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb2mmgg5.fsf@toke.dk \
--to=toke@toke.dk \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.