Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] tp-link archer c7 & cake & mac80211 fq_codel
Date: Thu, 12 May 2016 20:58:25 +0000	[thread overview]
Message-ID: <D57A2257-EA9F-4CF3-8D5B-88F2FE8E6AC1@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <5734E8C1.7090708@darbyshire-bryant.me.uk>

[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]

Oh and forgot, will mean you'll need this patch https://github.com/kdarbyshirebryant/ceropackages-3.10/commit/f26596763b3aecf2f6ec6a2401efe4d6966ecf27 if you want to build cake on lede's 4.4 bacported fq Codel fixes



On 12 May 2016, at 21:34, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk<mailto:kevin@darbyshire-bryant.me.uk>> wrote:



On 11/05/16 23:39, Dave Taht wrote:
On Wed, May 11, 2016 at 3:15 PM, Kevin Darbyshire-Bryant
<kevin@darbyshire-bryant.me.uk<mailto:kevin@darbyshire-bryant.me.uk>> wrote:
Forgot to mention - in slightly better news, the recent fq_codel
flows_cnt = 128 recommendation from Eric has made it up into John
I still kind of disagree with the reasoning on cutting the default to
128 queues, btw, but I felt it was worth testing.

IMHO in most circumstances having more queues will make you more
resilient to simple dumb floods as well as more complex ones, and give
better latency overall for all flows... But, lacking data on lower end
platforms, and being only willing to argue with y'all - (especially
eric), with it...

... is sort of why you find me (successfully) installing lede today on
the archer c7 v2.

I certainly agree strongly with the bulk drop portion of the patch. I
never liked scanning all the queues for every drop... I just couldn't
force myself to come up with something as drastic as eric did.

I sure wish cake, tc-adv, and the current sqm were up in lede...
The bulk drop has just gone in as a patch to 4.4 on LEDE.
https://git.lede-project.org/?p=source.git;a=commit;h=fad8bdfa40df8636a52d770bbab010086c1976ec


_______________________________________________
Cake mailing list
Cake@lists.bufferbloat.net<mailto:Cake@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/cake

[-- Attachment #2: Type: text/html, Size: 3941 bytes --]

      reply	other threads:[~2016-05-12 20:58 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
2016-05-11 22:39   ` Dave Taht
2016-05-12 20:34     ` Kevin Darbyshire-Bryant
2016-05-12 20:58       ` Kevin Darbyshire-Bryant [this message]

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=D57A2257-EA9F-4CF3-8D5B-88F2FE8E6AC1@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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