Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Other codel decay issues
Date: Sun, 12 Apr 2015 15:14:54 -0700	[thread overview]
Message-ID: <CAA93jw7srRMzA01ih67tEhSdZRdKdr44cuG56waDeJ5u1gM+fw@mail.gmail.com> (raw)

Codel state variable decay is an issue. I did not poke
into the 8 way set associative cache worked, but...

Queues empty and fill at lower rates as well, you DO
want to reuse the codel queue that was going into in
that case.

Eric settled on about 3 seconds to gc sch_fq; most
codel versions reset their state at 1600ms empty.

You probably want a "fresh" codel queue for each new
flow, or one borrowing from other existing states.

(I actually do like pie sometimes, just measuring the
total queue and then trying to find an ideal drop rate)
-- 
Dave Täht
Open Networking needs **Open Source Hardware**

https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67

             reply	other threads:[~2015-04-12 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12 22:14 Dave Taht [this message]
2015-04-12 23:22 ` Jonathan Morton

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=CAA93jw7srRMzA01ih67tEhSdZRdKdr44cuG56waDeJ5u1gM+fw@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