From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] tp-link archer c7 & cake & mac80211 fq_codel
Date: Wed, 11 May 2016 23:15:40 +0100 [thread overview]
Message-ID: <5733AF0C.8090200@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw7YeHhYsU6OhBH4XsUueNHA0qzoN4Wo8NwRw+SZPzbcpw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
Forgot to mention - in slightly better news, the recent fq_codel
flows_cnt = 128 recommendation from Eric has made it up into John
Crispin's lede staging tree, so I hope that'll appear in master soon.
The fq_codel 'batch drop' has sort of made it back to lede 4.4...well
there's 2 patches, one is a backport which also includes the api update
to support "update backlog for hierarchical qdiscs" as well as the batch
drop (not done by me), there's a version which I did which just
backports the batch drop.
The batch drop alone to 4.1 is beyond me.
I'm slowly coming around to the opinion that the 'batch drop alone'
patch is what should temporarily go into lede/openwrt until an official
backport is done. I'm not totally convinced about backporting the API
change.
On 11/05/16 22:53, Dave Taht wrote:
> looks like it can be easily flashed once again as 49217...
>
> https://wiki.openwrt.org/toh/tp-link/archer-c5-c7-wdr7500
>
> but Arokh's comprehensive build (which includes sch_cake):
> https://forum.openwrt.org/viewtopic.php?id=50914
>
> is a bit out of date...
>
> so I guess I should try lede for the first time via
> https://downloads.lede-project.org/snapshots/targets/ar71xx/generic/
>
> and try cross compiling sch_cake for it.
>
> ... and if I feel really, really, really, really ambitious, try
> backporting one of michals lovely patchsets to 4.4.
>
> http://blog.cerowrt.org/post/fq_codel_on_ath10k/
>
> https://github.com/kazikcz/linux/tree/fqmac-v4+dqlrfc+cpuregrfix
>
> But I don't feel that ambitious. It *will* be good to blow the dust
> off of the tp-link that made me go to Washington...
>
> here goes...
>
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next prev parent reply other threads:[~2016-05-11 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 21:53 Dave Taht
2016-05-11 22:05 ` Kevin Darbyshire-Bryant
2016-05-11 22:15 ` Kevin Darbyshire-Bryant [this message]
2016-05-11 22:39 ` Dave Taht
2016-05-12 20:34 ` Kevin Darbyshire-Bryant
2016-05-12 20:58 ` Kevin Darbyshire-Bryant
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5733AF0C.8090200@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@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