From: Adrian Chadd <adrian@freebsd.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Jonathan Morton" <chromatix99@gmail.com>,
make-wifi-fast@lists.bufferbloat.net,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"Toke Høiland-Jørgensen" <toke@toke.dk>
Subject: Re: [Make-wifi-fast] [ath9k-devel] Diagram of the ath9k TX path
Date: Tue, 10 May 2016 00:17:56 -0700 [thread overview]
Message-ID: <CAJ-Vmon6P_VakbhXY_YiLXZ3qq4JTr4xATPSKrg10DQFf-XyGw@mail.gmail.com> (raw)
In-Reply-To: <CAJ-Vmomd06KQba4vynVFyPZ9=e6mkT6ppzWHGesrJ_Nnc2AoPg@mail.gmail.com>
The other hack that I've seen ath9k do is they actually assign
sequence numbers and CCMP IVs at the point of enqueue-to-hardware,
rather than enqueue-to-driver. I tried this in FreeBSD and dropped it
for other reasons, mostly in favour of shallower (configurable!)
per-station queue depths.
That way you /could/ drop data frames in the driver/wifi stack
per-STA/TID queues as part of queue discipline, way before it gets
sent out on the air. If you're modeling airtime on the fly then you
could see the queue for a given station is way too deep now that the
rate to it has dropped, so don't bother keeping those frames around.
Once you have assigned the seqno/IV then you're "committed" so to speak.
-adrian
next prev parent reply other threads:[~2016-05-10 7:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 11:00 [Make-wifi-fast] " Toke Høiland-Jørgensen
2016-05-09 15:35 ` Dave Taht
2016-05-10 2:25 ` Jonathan Morton
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 [this message]
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=CAJ-Vmon6P_VakbhXY_YiLXZ3qq4JTr4xATPSKrg10DQFf-XyGw@mail.gmail.com \
--to=adrian@freebsd.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=chromatix99@gmail.com \
--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