Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: make-wifi-fast@lists.bufferbloat.net,
	 Michal Kazior <michal.kazior@tieto.com>
Subject: Re: [Make-wifi-fast] net-next is next
Date: Sat, 1 Oct 2016 11:59:44 -0700	[thread overview]
Message-ID: <CAA93jw5_5TQ6dWS_XXcus7=NmRjDRvFeZ4wxx1ysD4W5J7aA9Q@mail.gmail.com> (raw)
In-Reply-To: <8760pc9c0k.fsf@toke.dk>

OK, so the only thing I don't have a full grip on is what the
napi-for-ath10k change did.

On Sat, Oct 1, 2016 at 11:09 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> 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.

Patches somewhere?

> 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).

I was more or less planning to ignore that. Nobody else bothers to
test flooding the hardware queues, why should we? :/ And the behavior
is better now, regardless. Can't we ignore it? :-P

>Also, moving parts of the
> code into mac80211 would make it easier to re-use in other drivers. Not
> sure which parts, though.

same here. Pursuing another chipset (like the mt76 or "c.h.i.p") might
lend insight. Sigh.

>> * 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.

I outlined a couple approaches in my previous (overlong, meandering)
blog entry ( http://blog.cerowrt.org/post/a_bit_about_bbr/ ) -
notably, "giving up" - and turning off codel at a decent sized
aggregate for the station, rather than at the global limit of one
packet.

And there were a few much easier things from layering on top of the
airtime fairness stuff that might make the impact of multiple stations
on codel less difficult - reducing the txop and reducing the
advertised txop - when highly contended.

Assembling enough pieces to tackle and test those approaches at slow,
middle, and fast rates... would be good, and hopefully I've got a grip
on which pieces, now, thx.

>
>> As for what's in lede.... ?
>
> LEDE has the previous version of the mac80211 fix and the ath9k patch to
> enable the TXQ.

That's lede, not lede-staging?

>
> -Toke



-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

  parent reply	other threads:[~2016-10-01 18:59 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
2016-10-01 18:28   ` Dave Taht
2016-10-01 18:59   ` Dave Taht [this message]
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='CAA93jw5_5TQ6dWS_XXcus7=NmRjDRvFeZ4wxx1ysD4W5J7aA9Q@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=michal.kazior@tieto.com \
    --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