General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Daniel Sterling <sterling.daniel@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Jonathan Morton via Bloat" <bloat@lists.bufferbloat.net>,
	"Jonathan Morton" <chromatix99@gmail.com>,
	"Bjørn Ivar Teigen" <bjorn@domos.no>
Subject: Re: [Bloat] Researchers discover major roadblock in alleviating network congestion
Date: Thu, 4 Aug 2022 19:46:04 -0400	[thread overview]
Message-ID: <CAJZMiuce845VnbNWsKiqS7XZgBC5KaptxnW+oOpuQPxWMhzWww@mail.gmail.com> (raw)
In-Reply-To: <20220804162440.57fd5201@hermes.local>

"Flow control power is non-decentralizable" is from -- 1981? So we've
known for 40 years that TCP streams won't play nicely with each other
unless you shape them at the slower endpoint-- am I understanding that
correctly? But we keep trying anyway? :)

On Thu, Aug 4, 2022 at 7:24 PM Stephen Hemminger via Bloat
<bloat@lists.bufferbloat.net> wrote:
>
> On Fri, 5 Aug 2022 00:45:12 +0300
> Jonathan Morton via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> > > On 4 Aug, 2022, at 3:21 pm, Bjørn Ivar Teigen via Bloat <bloat@lists.bufferbloat.net> wrote:
> > >
> > > Main take-away (as I understand it) is something like "In real-world networks, jitter adds noise to the end-to-end delay such that any algorithm trying to infer congestion from end-to-end delay measurements will occasionally get it wrong and this can lead to starvation". Seems related to Jaffe's work on network power (titled "Flow control power is non-decentralizable").
> >
> > Hasn't this been known for many years, as a consequence of experience with TCP Vegas?
> >
> >  - Jonathan Morton
>
> It seems like BBR developers thought they could do better. Unfortunately, papers with negative
> results never seem to get written or published ;-(
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat

  reply	other threads:[~2022-08-04 23:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 12:21 Bjørn Ivar Teigen
2022-08-04 21:45 ` Jonathan Morton
2022-08-04 23:24   ` Stephen Hemminger
2022-08-04 23:46     ` Daniel Sterling [this message]
2022-08-05  0:25       ` Dave Collier-Brown
2022-08-07 14:10       ` Jonathan Morton
2022-08-08 15:34         ` Michael Richardson

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=CAJZMiuce845VnbNWsKiqS7XZgBC5KaptxnW+oOpuQPxWMhzWww@mail.gmail.com \
    --to=sterling.daniel@gmail.com \
    --cc=bjorn@domos.no \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=stephen@networkplumber.org \
    /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