From: Dave Taht <dave@taht.net>
To: Pete Heist <peteheist@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] [RFC PATCH 4/5] q_netem: support delivering packets in delayed time slots
Date: Tue, 21 Nov 2017 10:52:57 -0800 [thread overview]
Message-ID: <87fu97v4za.fsf@nemesis.taht.net> (raw)
In-Reply-To: <037FE91B-5F27-4CAD-AB56-24ED829C08F0@gmail.com> (Pete Heist's message of "Mon, 20 Nov 2017 10:02:28 +0100")
Pete Heist <peteheist@gmail.com> writes:
> On Nov 19, 2017, at 9:41 PM, Dave Taht <dave@taht.net> wrote:
>
>
>
> Yep with bql. I hadn’t thought about mq before. What my qos setup scripts
> are
> doing though is replacing the root qdisc (which now I see defaults to
> mq) with a
> single cake instance. With bql, should rather be leaving mq and putting
> four
> cake instances underneath it?
>
> Only if you want unlimited mode, and birthday problems, and don't have
> cpu to burn.
>
>
> Ok, if I compare the two, latency under load for rrul_be looks “better”
> (~1-1.5ms instead of ~3ms) with a single “cake unlimited besteffort lan”
> instance instead of four of them underneath mq.
Yep. Adding more unmanaged queues doesn't help. However it should spread
the load across more cpus.
next prev parent reply other threads:[~2017-11-21 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1042.1510953593.3609.cake@lists.bufferbloat.net>
2017-11-18 13:18 ` Pete Heist
2017-11-18 19:02 ` Dave Taht
2017-11-19 18:48 ` Pete Heist
2017-11-19 20:41 ` Dave Taht
2017-11-20 9:02 ` Pete Heist
2017-11-21 18:52 ` Dave Taht [this message]
2017-11-20 2:56 ` [Cake] Cleaning up cake Dave Taht
2017-11-17 21:19 [Cake] [RFC PATCH 0/5] patches for iproute2-net-next for netem slotting and cake Dave Taht
2017-11-17 21:19 ` [Cake] [RFC PATCH 4/5] q_netem: support delivering packets in delayed time slots 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/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=87fu97v4za.fsf@nemesis.taht.net \
--to=dave@taht.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=peteheist@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