From: Dave Taht <dave.taht@gmail.com>
To: cloneman <bufferbloat@flamingpc.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Does VDSL interleaving+FEC help bufferbloat?
Date: Fri, 4 Jan 2019 09:10:47 -0800 [thread overview]
Message-ID: <CAA93jw6Sct=zuRHo2KdRqFhvMO-EYyKwrpxziSkd45w0TdxN7g@mail.gmail.com> (raw)
In-Reply-To: <CABQZMoLhpvaFcDbZeWgpmjzPRCYCMrOtjAzM_Q7+9W6_N8h6cA@mail.gmail.com>
dsl interleave was added primarily to make multicast udp tv streams
work better (as they are very intolerant of packet loss). Often (as in
free's implementation) these streams are "invisible" to the overlying
IP applications. It typically adds at least 6ms of delay to an already
slow technology.
Do measure unloaded latency with and without it on, it's been a long
time since I fiddled with it....
next prev parent reply other threads:[~2019-01-04 17:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 21:38 cloneman
2019-01-04 4:01 ` Jonathan Morton
2019-01-04 13:21 ` Simon Barber
2019-01-04 17:10 ` Dave Taht [this message]
2019-01-04 17:43 ` Mikael Abrahamsson
2019-01-04 17:52 ` Jan Ceuleers
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='CAA93jw6Sct=zuRHo2KdRqFhvMO-EYyKwrpxziSkd45w0TdxN7g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=bufferbloat@flamingpc.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