From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Seen in passing: mention of Valve's networking scheme and RFC 5348
Date: Wed, 4 Apr 2018 09:39:07 -0400 [thread overview]
Message-ID: <a8827dde-22cf-78dc-dc7d-abb2f444a8f6@rogers.com> (raw)
In-Reply-To: <CAGrdgiV-nZ73z1Mr_38eN9YE1xXNEVzduM_jiLBxsD+Od6iP5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]
The phenomenon is called "lava flow", and is a classic anti-pattern
illustrated at http://antipatterns.com/lavaflow.htm
Their approach to fixing is ancient, though: there are
correctness-preserving refactorings for some of the problem space.
Alas, I don't know if middleboxes are correctable... maybe if they are
ones which only care about the IP layer?
--dave
On 04/04/18 08:45 AM, Jesper Louis Andersen wrote:
> On Tue, Apr 3, 2018 at 5:04 PM Jim Gettys <jg@freedesktop.org
> <mailto:jg@freedesktop.org>> wrote:
>
> To get to really good RTT's (with low jitter), you still need
> fq_codel (or similar). You just can't get there by hacking TCP
> no matter how hard you try...
>
>
> I agree with you on all points here. However, any change which patches
> an existing bad system is far more likely to win in the long run, also
> if it is bad in some way. Momentum is a killer of good solutions. I
> wish I had a ramification for this observation, but I currently don't.
>
> My hunch is that every new generation of young programmers wants to
> put their mark on the system. As a result, they take what worked well
> on level N-1 and proceed to build N on top of it. But the beanstalk
> never withers, so each level is present in said stack, still, after
> all these years.
>
> (Aside: The codel approach also has worked really well for me
> internally in Erlang systems as a way to maintain queue load. Far
> better than many other flow control schemes).
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net | -- Mark Twain
[-- Attachment #2: Type: text/html, Size: 3548 bytes --]
next prev parent reply other threads:[~2018-04-04 13:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tag:www.oreilly.com, 2018-04-02:/ideas/four-short-links-2-april-2018@localhost.localdomain>
2018-04-02 12:46 ` David Collier-Brown
2018-04-03 11:54 ` Jesper Louis Andersen
2018-04-03 12:14 ` Jonathan Morton
2018-04-03 12:35 ` Mikael Abrahamsson
2018-04-03 14:27 ` Michael Welzl
2018-04-03 14:48 ` Jesper Louis Andersen
2018-04-03 15:04 ` Jim Gettys
2018-04-04 12:45 ` Jesper Louis Andersen
2018-04-04 13:39 ` David Collier-Brown [this message]
2018-04-03 16:14 ` Michael Welzl
2018-04-04 7:01 ` Mikael Abrahamsson
2018-04-04 7:42 ` Dave Taht
2018-04-04 7:55 ` Michael Welzl
2018-04-04 8:53 ` Mikael Abrahamsson
2018-04-04 8:52 ` Mikael Abrahamsson
2018-04-04 9:56 ` Luca Muscariello
2018-04-04 10:52 ` Mikael Abrahamsson
2018-04-04 11:06 ` Luca Muscariello
2018-04-05 0:04 ` Marcelo Ricardo Leitner
2018-04-04 19:23 ` Michael Richardson
2018-04-04 19:38 ` Michael Welzl
2018-04-05 0:08 ` Marcelo Ricardo Leitner
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=a8827dde-22cf-78dc-dc7d-abb2f444a8f6@rogers.com \
--to=davec-b@rogers.com \
--cc=bloat@lists.bufferbloat.net \
--cc=davecb@spamcop.net \
/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