From: Neil Davies <neil.davies@pnsol.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: bloat <bloat@lists.bufferbloat.net>,
Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [Bloat] curious.....
Date: Sun, 8 Dec 2013 16:01:23 +0000 [thread overview]
Message-ID: <F819B9A5-6610-4978-9EAC-53C960B26A32@pnsol.com> (raw)
In-Reply-To: <09D8F3A0-7172-4677-9887-119813E28740@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On 8 Dec 2013, at 10:40, Sebastian Moeller <moeller0@gmx.de> wrote:
> ...
> Is that really true? given enough concurrent flows, critical flows might be delayed purely be the round robin scheduling of equally "worthy" packets in fq_codel, so some residual priory system might still make sense…
\x10
Sebastian - you are describing a property that we've measured in large scale (countrywide) deployed networks, it is also the underlying property that is causing mobile network operators issues with packet based networks as backhaul, as well as several other mission critical environments we've had dealings with.
When I pointed out that such service approaches will create extreme non-stationarity (in the particular case 2+ seconds) - the designers said - not their problem, not in their brief from management, they were told to bandwidth share.
It is not just that the 2+ seconds can exist, but that the overall system (under the right offered traffic pattern) WILL display that dynamic property.
Neil
[-- Attachment #2: Type: text/html, Size: 1515 bytes --]
next prev parent reply other threads:[~2013-12-08 16:01 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 18:40 Outback Dingo
2013-12-03 22:25 ` Kenyon Ralph
2013-12-04 0:25 ` Outback Dingo
2013-12-04 0:38 ` Dave Taht
2013-12-06 17:19 ` Juliusz Chroboczek
2013-12-06 18:15 ` Dave Taht
2013-12-07 11:24 ` Sebastian Moeller
2013-12-10 19:05 ` Dave Taht
2013-12-11 10:44 ` Sebastian Moeller
2013-12-07 12:59 ` Juliusz Chroboczek
2013-12-08 1:27 ` Steinar H. Gunderson
2013-12-08 5:24 ` Mikael Abrahamsson
2013-12-08 11:00 ` Mark Constable
2013-12-08 14:01 ` Outback Dingo
2013-12-08 14:03 ` Outback Dingo
2013-12-08 16:44 ` Mark Constable
2013-12-08 19:00 ` Sebastian Moeller
2013-12-08 13:12 ` Juliusz Chroboczek
2013-12-08 16:46 ` Jonathan Morton
2013-12-08 16:51 ` Dave Taht
2013-12-08 17:56 ` Juliusz Chroboczek
2013-12-08 21:05 ` Jonathan Morton
2013-12-08 14:22 ` Aaron Wood
2013-12-08 14:41 ` Jim Gettys
2013-12-08 10:40 ` Sebastian Moeller
2013-12-08 13:25 ` Juliusz Chroboczek
2013-12-08 16:26 ` Sebastian Moeller
2013-12-08 17:47 ` Juliusz Chroboczek
2013-12-08 19:02 ` Sebastian Moeller
2013-12-22 1:38 ` Dan Siemon
2013-12-22 3:46 ` Stephen Hemminger
2013-12-08 19:01 ` Jonathan Morton
2013-12-08 19:21 ` Sebastian Moeller
2013-12-08 16:01 ` Neil Davies [this message]
2013-12-08 20:41 Hal Murray
2013-12-08 23:16 ` Stephen Hemminger
2013-12-09 9:51 ` Sebastian Moeller
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=F819B9A5-6610-4978-9EAC-53C960B26A32@pnsol.com \
--to=neil.davies@pnsol.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jch@pps.univ-paris-diderot.fr \
--cc=moeller0@gmx.de \
/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