From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] l4s thoughts
Date: Mon, 2 Jul 2018 13:06:51 -0700 [thread overview]
Message-ID: <CAA93jw5UsVnknt0_Rp3Br3QDKbBWRLkDhKNbCO4-ukUQJmpV8w@mail.gmail.com> (raw)
whenever I get some time (and the right tcp patches) is fiddle with
two l4s approaches in fq_codel. The easy one is to leverage
ce_threshold,
accepting 1ms of queuing delay.
A better one, I think is to leverage the sparse flows optimization in
fq_codel to always mark when it's an old flow, and never mark when
it's new. That appears to be the most scalable, down to us or less.
Both ideas would take some work to do in cake, and I lack time and the
dctcp patches to try it.
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
reply other threads:[~2018-07-02 20:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw5UsVnknt0_Rp3Br3QDKbBWRLkDhKNbCO4-ukUQJmpV8w@mail.gmail.com \
--to=dave.taht@gmail.com \
--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