From: Jonathan Morton <chromatix99@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Martin Geddes <mail@martingeddes.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat in high resolution + non-stationarity
Date: Tue, 28 Nov 2017 18:16:44 +0200 [thread overview]
Message-ID: <CAJq5cE0biajRdUuQjA-J5BttC4Mk=OY+7oJ_E6CZ75fwa=iP3A@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE2jqAzAWoQB+3b9smq4ZvmBLoC5xE3oFYcQ+OVB+JCYgg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
I read the paper just now, and skimmed through the thesis to determine that
it was talking about the same thing using an order of magnitude more space.
It boils down to a Diffserv implementation using a classifier (details
handwaved as usual), policers, shapers, and a strict-priority tail-dropping
queue. The only noteworthy feature is that the position of the queue's
tail depends on the "cherish" metric of each traffic class, which is used
to provide differentiation in loss, leaving the strict-priority mechanism
to provide "urgency" (delay) differentiation.
From the above, you might reasonably conclude that I'm not very impressed.
The paper includes a test scenario versus a plain FIFO and a DRR system.
The DRR was weighted with a-priori knowledge of the relative traffic
volumes, which in fact would have degraded its performance in delay
management. A DRR++ implementation *without* such knowledge would have
outperformed it substantially.
Toke, reproducing that test load and running it through an unmodified Cake
instance would perhaps be enlightening.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 1233 bytes --]
next prev parent reply other threads:[~2017-11-28 16:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 20:23 Martin Geddes
2017-11-26 12:20 ` Toke Høiland-Jørgensen
2017-11-27 23:16 ` Martin Geddes
2017-11-27 23:55 ` Dave Taht
2017-11-28 2:07 ` Aaron Wood
2017-11-28 11:03 ` Toke Høiland-Jørgensen
[not found] ` <CAJq5cE3rWztd0f307bb-3H_tp5pvaHX_7Vp++PiwcU1X5eB_BQ@mail.gmail.com>
[not found] ` <CAJq5cE2jqAzAWoQB+3b9smq4ZvmBLoC5xE3oFYcQ+OVB+JCYgg@mail.gmail.com>
2017-11-28 16:16 ` Jonathan Morton [this message]
2017-11-30 12:31 ` Neil Davies
2017-11-30 16:51 ` Jonathan Morton
2017-11-30 19:59 ` Mikael Abrahamsson
2017-11-30 20:09 ` Jonathan Morton
2017-12-01 9:06 ` Michael Welzl
[not found] ` <CAJq5cE2_aiiJGdPOHQnEbfOqPVKLRP05AW1X6XLwSNaU233h=w@mail.gmail.com>
2017-12-01 13:48 ` Jonathan Morton
2017-11-28 23:57 ` Martin Geddes
2017-11-29 11:57 ` Toke Høiland-Jørgensen
-- strict thread matches above, loose matches on Subject: below --
2017-10-11 13:00 Martin Geddes
2017-10-16 20:26 ` 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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJq5cE0biajRdUuQjA-J5BttC4Mk=OY+7oJ_E6CZ75fwa=iP3A@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=mail@martingeddes.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