From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Best practices for paced TCP on Linux?
Date: Sat, 7 Apr 2012 22:16:08 +0200 [thread overview]
Message-ID: <20120407201608.GA21430@uio.no> (raw)
In-Reply-To: <CAA93jw6BL=zR-o5Kk0bS8NSc5F0wQmbGe0soY7_xAfUaGMXEDw@mail.gmail.com>
On Sat, Apr 07, 2012 at 12:38:04PM -0700, Dave Taht wrote:
> As for an explanation...
>
> Welcome to bufferbloat, the global plague that is sweeping the world!
Aaa. I already follow the bufferbloat discussion (although most of it is over
my head; even though my degree is in communications technology, I went down
the DSP path and not networking), but I really didn't expect bufferbloat to
actually be the direct cause of all of this. :-)
> It will make a great case study, and I would love it of a few of the
> amazing graphics and sound talents you had at "the gathering" - could
> lend their vision to explaining what bufferbloat is!
>
> jg's videos are helpful but they don't rock out to techno! nor do they
> feature led-lit juggling balls (wow!), nor spectral snakes that
> dissolve into visual madness.
Not speaking Norwegian, I think you missed the most important part about the
juggling balls -- they contain Arduinos with gravity sensors etc.. The
spectral snakes sound very much like Struct by Outracks, which was indeed
shown (it got 3rd place in the democompo last year).
> Perhaps using an rtp based streaming method, particularly over ipv6,
> will give you a better result next year.
RTP/RSTP would be interesting, although I have no experience with it
properly. How does it work wrt. yielding to TCP? How well does it traverse
NATs? (We do full stack and have done for years, but unfortunately most of
our external audience has no IPv6 yet.)
The intro compo is starting soon, and then the demo compo (right now,
freestyle video).
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2012-04-07 20:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 21:37 Steinar H. Gunderson
2012-04-06 21:49 ` Dave Taht
2012-04-06 22:21 ` Steinar H. Gunderson
2012-04-07 15:08 ` Eric Dumazet
2012-04-07 15:25 ` Dave Taht
2012-04-07 15:35 ` Steinar H. Gunderson
2012-04-07 15:48 ` Dave Taht
2012-04-07 15:52 ` Dave Taht
2012-04-07 17:10 ` Jonathan Morton
2012-04-07 17:18 ` Dave Taht
2012-04-07 17:44 ` Jonathan Morton
2012-04-07 18:10 ` Steinar H. Gunderson
2012-04-07 18:27 ` Jonathan Morton
2012-04-07 18:56 ` Dave Taht
2012-04-07 18:50 ` Dave Taht
2012-04-07 18:54 ` Steinar H. Gunderson
2012-04-07 19:01 ` Steinar H. Gunderson
2012-04-07 19:08 ` Jonathan Morton
2012-04-07 19:38 ` Dave Taht
2012-04-07 20:16 ` Steinar H. Gunderson [this message]
2012-04-14 0:37 ` Rick Jones
2012-04-07 21:13 ` Jesper Dangaard Brouer
2012-04-07 21:31 ` Steinar H. Gunderson
2012-04-07 19:02 ` Dave Taht
2012-04-07 21:49 ` Fred Baker
2012-04-07 22:36 ` Dave Taht
2012-04-07 23:59 ` Fred Baker
2012-04-07 20:27 ` Neil Davies
2012-04-14 0:35 ` Rick Jones
2012-04-14 21:06 ` Roger Jørgensen
2012-04-16 17:05 ` Rick Jones
2012-04-07 11:54 ` Neil Davies
2012-04-07 14:17 ` Fred Baker
2012-04-07 15:08 ` Neil Davies
2012-04-07 15:16 ` Steinar H. Gunderson
2012-04-14 0:44 ` Rick Jones
2012-04-07 14:48 ` Dave Taht
2012-05-12 20:08 ` Steinar H. Gunderson
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=20120407201608.GA21430@uio.no \
--to=sgunderson@bigfoot.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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