From: Neil Davies <neil.davies@pnsol.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Detecting bufferbloat from outside a node
Date: Mon, 27 Apr 2015 21:38:21 +0100 [thread overview]
Message-ID: <C4D6E725-57CA-4A71-95F9-35AC1892A96F@pnsol.com> (raw)
In-Reply-To: <874mo11sdf.fsf@toke.dk>
Toke
∆Q is both the concept (quallity attenuation - the fact that delay and potential for loss is both conserved and only every increases[1]) and for its representation as an improper random variable (one who's CDF doesn't necessarily reach one).
One of my adages is that "network quality" doesn' t exist - just like you can't buy a box of "dark" and make a room dark by opening the box, you can't buy a box of "network quality" - delivering quality in networks is managing (through bounding) the "quality attenuation"
Neil
[1] Delay and loss can be traded - i.e resends or even forward error correction - but you can't reduce the ∆Q - resends mean increased delay to cover loss, forward error correction means increased delay to cover bit error rates) etc This is true at any (and all layers) and in *every* queueing and scheduling mechanism, just one of those nasty universal properties that we can't get away from.
On 27 Apr 2015, at 16:51, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Neil Davies <neil.davies@pnsol.com> writes:
>
>> Depends on your starting point:
>
> Right, having looked a bit more at this:
>
>> - if it is "how does this relate to the end user" - look at "the
>> properties and mathematics of data transport quality"
>
> This mentions, on slide 30, an analytical model for predicting (changes
> in) ∆Q. Is this Judy Holyer's "A Queueing Theory Model for Real Data
> Networks", or does it refer to something else?
>
> -Toke
next prev parent reply other threads:[~2015-04-27 20:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 9:48 Paolo Valente
2015-04-27 9:54 ` Neil Davies
2015-04-27 10:45 ` Toke Høiland-Jørgensen
2015-04-27 10:57 ` Neil Davies
2015-04-27 14:22 ` Toke Høiland-Jørgensen
2015-04-27 20:27 ` Neil Davies
2015-04-27 15:51 ` Toke Høiland-Jørgensen
2015-04-27 20:38 ` Neil Davies [this message]
2015-04-27 21:37 ` Toke Høiland-Jørgensen
2015-04-28 7:14 ` Neil Davies
2015-04-27 11:54 ` Paolo Valente
2015-04-27 15:25 ` Jonathan Morton
2015-04-27 20:30 ` Neil Davies
2015-04-27 23:11 ` Jonathan Morton
2015-04-28 7:17 ` Neil Davies
2015-04-28 9:58 ` Sebastian Moeller
2015-04-28 10:23 ` Neil Davies
2015-05-04 10:10 ` Paolo Valente
2015-05-04 10:21 ` Neil Davies
2015-05-04 10:28 ` Jonathan Morton
2015-05-04 10:41 ` Paolo Valente
2015-05-04 10:44 ` Neil Davies
2015-05-04 10:42 ` Neil Davies
2015-05-04 11:33 ` Jonathan Morton
2015-05-04 11:39 ` Neil Davies
2015-05-04 12:17 ` Jonathan Morton
2015-05-04 12:35 ` Neil Davies
2015-05-04 17:39 ` David Lang
2015-05-04 19:09 ` Jonathan Morton
2015-04-28 16:05 ` Rick Jones
2015-04-27 20:13 ` Neil Davies
2015-04-27 9:57 ` Toke Høiland-Jørgensen
2015-04-27 10:10 ` Paolo Valente
2015-04-27 10:19 ` Paolo Valente
2015-04-27 10:23 ` Toke Høiland-Jørgensen
2015-04-27 10:53 ` Paolo Valente
2015-04-27 20:39 ` David Lang
2015-05-04 10:31 ` Paolo Valente
2015-04-27 10:26 ` Neil Davies
2015-04-27 10:32 ` Toke Høiland-Jørgensen
2015-04-27 10:38 ` Neil Davies
2015-04-27 10:52 ` Toke Høiland-Jørgensen
2015-04-27 11:03 ` Neil Davies
2015-04-27 12:03 ` Toke Høiland-Jørgensen
2015-04-27 20:19 ` Neil Davies
2015-05-19 21:23 ` Alan Jenkins
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=C4D6E725-57CA-4A71-95F9-35AC1892A96F@pnsol.com \
--to=neil.davies@pnsol.com \
--cc=bloat@lists.bufferbloat.net \
--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