From: Dave Taht <dave.taht@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [Make-wifi-fast] Diagram of the ath9k TX path
Date: Mon, 9 May 2016 08:35:41 -0700 [thread overview]
Message-ID: <CAA93jw5v0orW9hHsKw7LuL7HnN2eJUU4qYuh_oPUeV84qXZutg@mail.gmail.com> (raw)
In-Reply-To: <871t5bpkc7.fsf@toke.dk>
On Mon, May 9, 2016 at 4:00 AM, Toke H?iland-J?rgensen <toke@toke.dk> wrote:
> I finally finished my flow diagram of the ath9k TX path (corresponding
> to the previous one I did for the mac80211 stack). In case anyone else
> is interested, it's available here:
>
> https://blog.tohojo.dk/2016/05/the-ath9k-tx-path.html
Looks quite helpful. I do not understand why there is a "fast path" at
all in this driver, should we always wait a little bit to see if we
can
form an aggregate?
It would be awesome to be able to adapt michal's work on fq_codeling
things as he did here (leveraging rate control information)
http://blog.cerowrt.org/post/fq_codel_on_ath10k/
rather than dql as he did here:
http://blog.cerowrt.org/post/dql_on_wifi_2/
to the ath9k.
> -Toke
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
Dave T?ht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next parent reply other threads:[~2016-05-09 15:35 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 ` Dave Taht [this message]
2016-05-10 2:32 ` [ath9k-devel] [Make-wifi-fast] Diagram of the ath9k TX path 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
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=CAA93jw5v0orW9hHsKw7LuL7HnN2eJUU4qYuh_oPUeV84qXZutg@mail.gmail.com \
--to=dave.taht@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).