From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
make-wifi-fast@lists.bufferbloat.net,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [Make-wifi-fast] Diagram of the ath9k TX path
Date: Tue, 10 May 2016 05:25:00 +0300 [thread overview]
Message-ID: <6ADC1A9D-72C9-47A5-BDC7-94C14ED34379@gmail.com> (raw)
In-Reply-To: <CAA93jw5v0orW9hHsKw7LuL7HnN2eJUU4qYuh_oPUeV84qXZutg@mail.gmail.com>
> On 9 May, 2016, at 18:35, Dave Taht <dave.taht@gmail.com> wrote:
>
> should we always wait a little bit to see if we can form an aggregate?
I thought the consensus on this front was “no”, as long as we’re making the decision when we have an immediate transmit opportunity.
If we *don’t* have an immediate transmit opportunity, then we *must* wait regardless, and maybe some other packets will arrive which can then be aggregated.
- Jonathan Morton
next prev parent reply other threads:[~2016-05-10 2:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 11:00 Toke Høiland-Jørgensen
2016-05-09 15:35 ` Dave Taht
2016-05-10 2:25 ` Jonathan Morton [this message]
2016-05-10 2:59 ` Dave Taht
2016-05-10 3:30 ` [Make-wifi-fast] [ath9k-devel] " Adrian Chadd
2016-05-10 4:04 ` Dave Taht
2016-05-10 4:22 ` Aaron Wood
2016-05-10 7:15 ` Adrian Chadd
2016-05-10 7:17 ` Adrian Chadd
2016-05-10 3:41 ` [Make-wifi-fast] " David Lang
2016-05-10 4:59 ` Dave Taht
2016-05-10 5:22 ` David Lang
2016-05-10 9:04 ` Toke Høiland-Jørgensen
2016-05-11 14:12 ` Dave Täht
2016-05-11 15:09 ` Dave Taht
2016-05-11 15:20 ` Toke Høiland-Jørgensen
2016-05-13 17:46 ` 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:20 ` 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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ADC1A9D-72C9-47A5-BDC7-94C14ED34379@gmail.com \
--to=chromatix99@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox