From: Jaap Buurman <jaapbuurman@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Airtime fairness patch merged upstream, and the Turris Omnia debloated
Date: Thu, 22 Dec 2016 20:06:03 +0100 [thread overview]
Message-ID: <CAN-r--=v50mLnO-u9FaNBDVuE2OFzM8hYepn1uKHwX-CiV-0eg@mail.gmail.com> (raw)
In-Reply-To: <f65e8ee8-6531-5fc1-7682-0047c3654c99@darbyshire-bryant.me.uk>
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
This is awesome news! This means that it will be included in the first
stable release that they have planned in the near future :)
Now the following question might sound stupid, but how difficult would it
be to apply these airtime fairness principles to Ath10k as well?
Is this planned? Or will this be a Ath9k feature only?
On Thu, Dec 22, 2016 at 6:53 PM, Kevin Darbyshire-Bryant <
kevin@darbyshire-bryant.me.uk> wrote:
>
>
> On 19/12/16 22:31, Toke Høiland-Jørgensen wrote:
>
>> The airtime fairness patch for ath9k has been accepted into the mainline
>> Linux kernel, and is queued to be merged for 4.11 (i.e. the next merge
>> window after the current 4.10 cycle completes).
>>
>> The patch has also been accepted into LEDE and is currently in Felix'
>> staging tree at
>> https://git.lede-project.org/?p=lede/nbd/staging.git;a=summary - so if
>> nothing surprising shows up, it should make it into the regular LEDE
>> nightlies before too long :)
>>
>
> It's escaped out of Felix's tree and is now in master. Snapshots will
> start to have that as default as the buildbots do their thang.
>
> Not a bad present really :-)
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
[-- Attachment #2: Type: text/html, Size: 2186 bytes --]
next prev parent reply other threads:[~2016-12-22 19:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 22:31 Toke Høiland-Jørgensen
2016-12-20 0:10 ` [Make-wifi-fast] [Cake] " Dave Taht
2016-12-20 1:23 ` Dave Taht
2016-12-20 1:22 ` Dave Taht
2016-12-22 17:53 ` [Make-wifi-fast] " Kevin Darbyshire-Bryant
2016-12-22 18:36 ` Dave Taht
2016-12-22 18:56 ` Aaron Wood
2016-12-22 19:06 ` Jaap Buurman [this message]
2016-12-22 20:48 ` Dave Taht
2016-12-22 22:03 ` Kevin Darbyshire-Bryant
2016-12-24 1:32 ` Aaron Wood
2016-12-24 1:41 ` [Make-wifi-fast] [Cake] " Dave Taht
2016-12-24 1:48 ` Aaron Wood
2016-12-24 1:59 ` Dave Taht
2016-12-24 2:01 ` Jonathan Morton
2016-12-24 2:03 ` Dave Taht
2016-12-24 2:18 ` Aaron Wood
2016-12-24 2:29 ` Dave Taht
2016-12-24 2:51 ` Aaron Wood
2016-12-24 3:17 ` Dave Taht
2016-12-24 14:03 ` Valent Turkovic
2016-12-25 17:06 ` Toke Høiland-Jørgensen
2016-12-25 17:16 ` Dave Täht
2016-12-25 18:41 ` Noah Causin
2016-12-25 19:18 ` Jaap Buurman
2016-12-24 2:07 ` Dave Taht
2016-12-24 2:15 ` Dave Taht
2016-12-24 2:18 ` Aaron Wood
2016-12-24 2:22 ` Aaron Wood
2016-12-24 2:24 ` Dave Taht
2016-12-24 2:25 ` Aaron Wood
2016-12-24 2:33 ` Dave Taht
2016-12-24 2:49 ` Aaron Wood
2016-12-24 2:31 ` 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='CAN-r--=v50mLnO-u9FaNBDVuE2OFzM8hYepn1uKHwX-CiV-0eg@mail.gmail.com' \
--to=jaapbuurman@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