General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Martin Geddes <mail@martingeddes.com>
Cc: Dave Taht <dave@taht.net>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat in high resolution + non-stationarity
Date: Tue, 28 Nov 2017 12:03:36 +0100	[thread overview]
Message-ID: <874lpe8y2f.fsf@toke.dk> (raw)
In-Reply-To: <CAAAY2aipf8BqdpbPr58xbSFKBiEycL0M6AtE-Qcm-Oat5ojFyA@mail.gmail.com>

Martin Geddes <mail@martingeddes.com> writes:

> The two critical references are this paper
> <http://www.pnsol.com/public/TP-PNS-2003-09.pdf> and this PhD thesis
> <https://www.cs.kent.ac.uk/pubs/2003/1892/>. The former describes
> "cherish-urgency" multiplexing. The "cherish" is what is different to
> today's scheduling. It is used to create a new class of algorithm
> whose goal is global optimisation, not local optimisation (and global
> pessimisation).

Cool, thanks; I'll add that to my reading list (well, the paper
certainly; not sure I'll get the time to go through the whole 200+ page
thesis anytime soon :/)

> The latter describes a paradigm change from "build it and then reason
> about emergent performance" to "reason about engineered performance
> and then build it". It works in practise
> <http://www.martingeddes.com/how-wales-got-the-first-internet-fast-lane/>,
> so whether it works in theory is left as an exercise to the reader.

I don't suppose there's an open source implementation available to play
with?

-Toke

  parent reply	other threads:[~2017-11-28 11:03 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 [this message]
     [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
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=874lpe8y2f.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave@taht.net \
    --cc=mail@martingeddes.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