From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] trivial 6in4 fix(?)
Date: Sun, 16 Jun 2013 22:32:07 +0200 [thread overview]
Message-ID: <EF6909B6-AB3C-4535-ACA2-730E2489037E@gmx.de> (raw)
In-Reply-To: <87bo75rgp5.fsf@toke.dk>
Hi Toke,
On Jun 16, 2013, at 21:36 , Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Dave Taht <dave.taht@gmail.com> writes:
>
>> Well, that result is mildly puzzling. netperf-wrapper -6 throughout?
>> no ipv4?
>
> There's some ipv4 traffic in the background. Dunno exactly how much.
>
>> You are on a dsl line, too? There has been some fixes to the overhead
>> issue that have landed but encapsulation atm is still borked (you
>> using atm?)
>
> Yeah. I'm on VDSL. No idea what encapsulation (and can't access my
> isp-provided router since that is in bridge mode).
As far as I can tell at least VDSL typically means VDSL2 and that probably means PTM instead of ATM. In essence this means you do not have to deal with ATMs 48 payload bytes per 53 byte cell transport inefficiencies. So all you need to deal with is per packet overhead. Then again I am sure you probably know that already. (Sidenote, as far as I understand (so not very far) using ATM for DSL connections with POTS service in the lower frequency range never made much sense at all, the 5 byte ATM header typically was constant and by that just ballast and the 48 byte quantization on the last mile never came with any benefits, but I digress)
Best
Sebastian
>
> -Toke
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2013-06-16 20:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 17:13 Dave Taht
2013-06-16 18:56 ` Toke Høiland-Jørgensen
2013-06-16 19:13 ` Dave Taht
2013-06-16 19:19 ` Dave Taht
2013-06-16 19:21 ` Toke Høiland-Jørgensen
2013-06-16 19:27 ` Dave Taht
2013-06-16 19:36 ` Toke Høiland-Jørgensen
2013-06-16 19:38 ` Toke Høiland-Jørgensen
2013-06-16 20:32 ` Sebastian Moeller [this message]
2013-06-16 20:55 ` Toke Høiland-Jørgensen
2013-06-16 20:57 ` Dave Taht
2013-06-16 20:58 ` Toke Høiland-Jørgensen
2013-06-17 7:35 ` Sebastian Moeller
2013-06-17 7:30 ` Sebastian Moeller
2013-06-17 9:44 ` Toke Høiland-Jørgensen
2013-06-17 10:40 ` Sebastian Moeller
2013-06-17 10:50 ` Toke Høiland-Jørgensen
2013-06-17 12:27 ` Sebastian Moeller
2013-07-09 15:06 ` Sebastian Moeller
2013-06-16 19:21 ` Dave Taht
2013-06-16 19:30 ` Toke Høiland-Jørgensen
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EF6909B6-AB3C-4535-ACA2-730E2489037E@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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