From: Jonathan Morton <chromatix99@gmail.com>
To: Jan Ceuleers <jan.ceuleers@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] ultrafast broadband conference june 27-30
Date: Sat, 18 Jun 2016 13:24:50 +0300 [thread overview]
Message-ID: <E975E03F-0256-42E2-84FE-5A124DBD807D@gmail.com> (raw)
In-Reply-To: <57652072.7020708@gmail.com>
> On 18 Jun, 2016, at 13:20, Jan Ceuleers <jan.ceuleers@gmail.com> wrote:
>
>> These buffers are not inherent to the link technology.
>> If they were, we’d be calling for different link technology.
>
> Thanks for confirming my suspicions. But this is exactly what Dave was
> doing, since he blamed the uplink bloat on "g.fast technologies".
>
> So it seems that you and I agree that it's not G.fast itself that is
> bloated, but the lack of proper buffer management in certain (most?) DSL
> modems, regardless of whether they support G.fast or some other flavour
> of DSL.
Right. We’re hoping that G.fast, being a new link technology, has taken on board some of the extensive research into buffer sizing and management, in typical device implementations. But we’re not holding our breath - the industry is rather stubborn on this point.
- Jonathan Morton
next prev parent reply other threads:[~2016-06-18 10:24 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
2016-06-18 10:09 ` Jonathan Morton
2016-06-18 10:20 ` Jan Ceuleers
2016-06-18 10:24 ` Jonathan Morton [this message]
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=E975E03F-0256-42E2-84FE-5A124DBD807D@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jan.ceuleers@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