From: Sebastian Moeller <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] pppoe-ptm overhead calculation question
Date: Thu, 3 Sep 2015 20:14:19 +0200 [thread overview]
Message-ID: <330FB5B1-B42F-4475-AFA2-C0303D916C00@gmx.de> (raw)
In-Reply-To: <CAJq5cE1H3iexcR3YJZtdKxC8Frexg9oJ+Ft2Tvt_pM63beQa1A@mail.gmail.com>
Hi Jonathan,
On Sep 3, 2015, at 20:02 , Jonathan Morton <chromatix99@gmail.com> wrote:
> I'm getting the distinct impression that VDSL1 & VDSL2 are completely different technologies with the misfortune of sharing an acronym and physical medium.
That is a decent way of putting it. VDSL2 has the advantage of coming late to the party and avoiding some of the then obvious warts of VDSL1; also VDSL1 ist not compatible with ADSL-lines in the same DSLAM and hence probably on the define world wide. There are some deployments in Asia and parts of the rest of the world (according to wikipedia) VDSL2 seems to have struck mor resonance with telco ISPs and hence seems more prevalent..
> It's certainly far too easy to confuse data about one for the other.
It certainly is, it does not help that ITU documents are decidedly not fun to read...
>
> Ideally, I'd like to see measurements on a real line to corroborate one way or the other.
The good thing is that I outlined the approach to measure this: create a traffic shaper close to line-rate, saturate the shaper with to-be-expanded-bytes packets and measure latency under load. For VDSL2 all should be well (or as well as with not-to-be-expanded bytes as payloads), for HDLC latency should rise quickly and badly (my first approximation would be that the on-the-wire-size doubles, so the shaper is toast by then).
> However, the use of a fixed-size word frame does sound much more elegant than HDLC.
64/65 encoding is not too bad actually 1.5% overhead independent of the number of packets is decent…
Best Regards
Sebastian
>
> - Jonathan Morton
prev parent reply other threads:[~2015-09-03 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 13:58 Sebastian Moeller
2015-09-03 18:02 ` Jonathan Morton
2015-09-03 18:14 ` Sebastian Moeller [this message]
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=330FB5B1-B42F-4475-AFA2-C0303D916C00@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@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