From: Jan Ceuleers <jan.ceuleers@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] ultrafast broadband conference june 27-30
Date: Sat, 18 Jun 2016 10:04:04 +0200 [thread overview]
Message-ID: <57650074.90106@gmail.com> (raw)
In-Reply-To: <CAA93jw4UPnTR8geArA0RdL1Z=ksTb6UiVhvi7EANo10NgZBtDg@mail.gmail.com>
On 13/06/16 18:05, Dave Taht wrote:
> Is anyone going to this? I sure hope the g.fast technologies have
> their uplink bloat fixed, at least.
Dave,
(Been trying to send this for the past few days unsuccessfully; perhaps
the DNS gremlins caused it to bounce. Now sending via gmail).
As I'm sure everyone here knows DSL uses interleaving in order to
achieve coding gain in the face of impulse noise. DSL has to operate in
environments that are rich in such noise so although it is possible to
turn interleaving off pretty much every operator has it on, if for no
other reason than to avoid IPTV artefacts.
This does not meet at least my understanding of the definition of
bufferbloat, in that interleaving introduces a static amount of latency
(i.e. latency that does not vary with load).
But it's perhaps also not what you were talking about because you
mentioned the uplink. Not sure what you meant. Still, other than the use
of ATM and coding I'm not aware of buffering in DSL. Certainly no
dynamic buffers that absorb traffic under load.
Could you enlighten me? I know that you're a busy man; a few keywords
for me to stick into google would be great.
Thanks, Jan
next prev parent reply other threads:[~2016-06-18 8:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 16:05 Dave Taht
2016-06-15 5:43 ` Pedro Tumusok
2016-06-18 8:04 ` Jan Ceuleers [this message]
2016-06-18 10:09 ` Jonathan Morton
2016-06-18 10:20 ` Jan Ceuleers
2016-06-18 10:24 ` Jonathan Morton
2016-06-18 10:38 ` Jan Ceuleers
2016-06-18 10:51 ` Toke Høiland-Jørgensen
2016-06-18 11:06 ` Jan Ceuleers
2016-06-18 11:14 ` Toke Høiland-Jørgensen
2016-06-18 11:22 ` Jan Ceuleers
2016-06-18 13:55 ` Jonathan Morton
2016-06-18 14:07 ` Dave Taht
2016-06-18 13:31 ` 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=57650074.90106@gmail.com \
--to=jan.ceuleers@gmail.com \
--cc=bloat@lists.bufferbloat.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