Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake flenter results round 1
Date: Mon, 27 Nov 2017 14:05:36 +0100	[thread overview]
Message-ID: <1C937A63-CEC1-4173-8812-EA2A85972B73@gmail.com> (raw)
In-Reply-To: <CAJq5cE2TDGfhFnyG9QujDZ3JFdv9fdT=qwPSCDzfe6vJv4tGUQ@mail.gmail.com>

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


> On Nov 27, 2017, at 1:18 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
> Here's the difference between "srchost" and "dual-srchost": the latter imposes per-flow fairness on traffic to each host, with a separate queue/AQM per flow like with "flows".  The former only has one queue/AQM per host.
> 
> Analogously for dsthost.
> 
> Then "hosts" mode allocates a separate queue for each host-pair encountered.
> 
> But "triple-isolate" isn't quite analogous to "hosts".  Instead it tries to heuristically behave like either of the dual modes, depending on which one is likely to be on the LAN side of the link.  This allows it to be a reasonable default setting, though the "dual" modes will perform more reliably if chosen correctly.
> 

Thanks, so as I understand it, fairness at the host level for srchost and dual-srchost should be the same, only with dual-srchost there should additionally be fairness among each host’s flows.

If that’s right, I’m confused by this result where there are four clients, each with a separate source IP connecting to the same server IP:

1: tcp_up with 1 flow
2: tcp_up with 12 flows
3: tcp_down with 1 flow
4: tcp_down with 12 flows

With srchost/dsthost it’s fair at the host level (easiest to look at TCP upload/TCP upload sum and TCP download/TCP download sum numbers at the bottom of the page):

http://www.drhleny.cz/bufferbloat/cake/round1/hostiso_eg_cake_src_cake_dst_900mbit/index.html <http://www.drhleny.cz/bufferbloat/cake/round1/hostiso_eg_cake_src_cake_dst_900mbit/index.html>

and with dual-srchost/dual-dsthost it’s not:

http://www.drhleny.cz/bufferbloat/cake/round1/hostiso_eg_cake_dsrc_cake_ddst_900mbit/index.html <http://www.drhleny.cz/bufferbloat/cake/round1/hostiso_eg_cake_dsrc_cake_ddst_900mbit/index.html>


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

  reply	other threads:[~2017-11-27 13:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 11:04 Pete Heist
2017-11-27 11:10 ` Toke Høiland-Jørgensen
2017-11-27 11:12   ` Pete Heist
2017-11-27 12:18     ` Jonathan Morton
2017-11-27 13:05       ` Pete Heist [this message]
2017-11-27 14:01         ` Jonathan Morton
2017-11-27 14:07           ` Pete Heist
2017-11-27 14:34             ` Pete Heist
2017-11-27 14:48               ` Jonathan Morton
2017-11-27 15:53                 ` Pete Heist
2017-11-27 16:17                   ` Georgios Amanakis
2017-11-27 17:32                     ` Pete Heist
2017-11-27 17:33                     ` Dave Taht
2017-11-27 17:34                       ` Sebastian Moeller
2017-11-27 17:38                         ` Dave Taht
2017-11-27 17:50                           ` Pete Heist
2017-11-27 17:35                       ` Pete Heist
2017-11-27 18:13     ` Dave Taht
2017-11-27 18:21       ` Pete Heist
2017-11-27 18:45 ` Pete Heist
2017-11-27 19:06   ` Georgios Amanakis
2017-11-27 20:37   ` Toke Høiland-Jørgensen
2017-11-27 20:50     ` Dave Taht
2017-11-27 20:53     ` Pete Heist
2017-11-27 21:08       ` Toke Høiland-Jørgensen
2017-11-27 21:17         ` Pete Heist

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=1C937A63-CEC1-4173-8812-EA2A85972B73@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=toke@toke.dk \
    /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