Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
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: Sun, 19 Nov 2017 12:41:27 -0800	[thread overview]
Message-ID: <8760a6rog8.fsf@nemesis.taht.net> (raw)
In-Reply-To: <4235D7B6-1CA6-4B57-BA00-97D3F7D44EFA@gmail.com> (Pete Heist's message of "Sun, 19 Nov 2017 19:48:58 +0100")

Pete Heist <peteheist@gmail.com> writes:

>> On Nov 18, 2017, at 8:02 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> 
>> On Sat, Nov 18, 2017 at 5:18 AM, Pete Heist <peteheist@gmail.com> wrote:
>>> 
>>> On Nov 17, 2017, at 11:55 PM,dave.taht@gmail.com wrote:
>>> 
>>> Slotting is a crude approximation of the behaviors of shared media such
>>> as cable, wifi, and LTE, which gather up a bunch of packets within a
>>> varying delay window and deliver them, relative to that, nearly all at
>>> once.
>>> 
>>> Nice…
>> 
>> Meh. It really is "crude", and I keeping kicking about ways to somehow
>> emulate half (or less) duplex, variable rates around a mean, mcast,
>> etc.
>> 
>> it IS very nice to have a rate limiter that actually behaves a bit
>> more like wifi, and I hope to also add the new ack fitering stuff to
>> it.
>
> I guess there may never be a way to make this perfect, only to try to reproduce
> the behavior that matters enough to make it usable for testing.
>
>>> One of the things I also notice in my LAN tests is latencies for different
>>> flows staying at more or less fixed (and different) positions relative to
>>> the mean in flent results. Those positions, and the mean, can change with
>>> each test run. Do you think this could result from the hashing to different
>>> hardware queues (four in my case) changing between test runs?
>> 
>> yes if you are using bql probably. Is it sch_mq on top?

Only if you want unlimited mode, and birthday problems, and don't have
cpu to burn.

>
> 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?
>
>>> And is it
>>> worth trying to simulate this effect, or not really?
>> 
>> Dunno. There are a couple ways to turn it off.
>
> Fair enough...
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake

  reply	other threads:[~2017-11-19 20:41 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 [this message]
2017-11-20  9:02         ` Pete Heist
2017-11-21 18:52           ` Dave Taht
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=8760a6rog8.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