From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] net-next is next
Date: Sat, 01 Oct 2016 20:09:47 +0200 [thread overview]
Message-ID: <8760pc9c0k.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw7jzfs+mn0fpjSPjuCkPgORcMfmEJmCjcSwTpZBJG5nvg@mail.gmail.com> (Dave Taht's message of "Fri, 30 Sep 2016 11:38:35 -0700")
Dave Taht <dave.taht@gmail.com> writes:
> I'm a little vague on the pieces missing as yet. I think?, still out
> of tree are:
Don't see anything missing from the list that I have been working on. Of
the things I have:
> * Hooking up the ath9k to the intermediate queues code
I expect Kalle to add this sometime during the upcoming merge window
(which opens tomorrow, according to the PHB crystal ball:
http://phb-crystal-ball.org/).
> * airtime fairness for the ath9k
Haven't submitted a new version of this since the other things went in.
While the basic scheduler works well, there are still some things to
work out before making a serious attempt at upstreaming it (most notably
the interaction with the hardware QoS queues). Also, moving parts of the
code into mac80211 would make it easier to re-use in other drivers. Not
sure which parts, though.
> * Codel "hack" for low rates
This still needs to be solved, but the hack I posted previously was just
that: A hack. I think a different approach is needed.
> As for what's in lede.... ?
LEDE has the previous version of the mac80211 fix and the ath9k patch to
enable the TXQ.
-Toke
next prev parent reply other threads:[~2016-10-01 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 18:38 Dave Taht
2016-10-01 18:09 ` Toke Høiland-Jørgensen [this message]
2016-10-01 18:28 ` Dave Taht
2016-10-01 18:59 ` Dave Taht
2016-10-01 19:05 ` Dave Taht
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=8760pc9c0k.fsf@toke.dk \
--to=toke@toke.dk \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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