From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] trivial 6in4 fix(?)
Date: Mon, 17 Jun 2013 12:50:53 +0200 [thread overview]
Message-ID: <874ncxnh82.fsf@toke.dk> (raw)
In-Reply-To: <2AD5FF25-5388-4AE7-8BE2-837B7F94250F@gmx.de> (Sebastian Moeller's message of "Mon, 17 Jun 2013 12:40:59 +0200")
[-- Attachment #1.1: Type: text/plain, Size: 1705 bytes --]
Sebastian Moeller <moeller0@gmx.de> writes:
> I fully believe you that it is flat (graph did not make it into my
> inbox…)
Heh. May have forgotten to attach it... Should be there now...
> So that looks like PTM. Good! But beware the expected step size
> depends on your down and uplink speeds, at VDSL I would only expect a
> very tiny increase (basically the time it takes to see an additional
> ATM cell back and forth, (RTT step per ATM cell in milliseconds =
> (53*8 / line.down.bit + 53*8 / line.up.bit ) * 1000); this means that
> potentially a large sample size per ping packet size is required to be
> reasonably sure that there is no step....
Right, well in my case that comes out as something like 0.05 ms, which
is way below the measuring accuracy of my ping test (lowest mdev as
reported by ping is 0.7ms; highest is 3.3). So I guess testing is not
really going to be viable in this case. But then perhaps it's not going
to make much of a difference either way in this case?
> Hence in theory using a saturating load and measuring the latencies
> for different overhead values should still work. I wonder whether rrul
> might just be the right probe? If you go that route I would be
> delighted to learn the outcome :). Sorry to be of no more help here.
Right. That seems reasonable. However, it also seems to require a bit
more testing than I really have the time to spare right now, so I think
I'll defer it for the time being. I wonder if it would be possible to
persuade my ISP to set up a netperf server to test against...
Either way, thanks for your insight; I'll be sure to ping you if I come
up with something more conclusive... :)
-Toke
[-- Attachment #1.2: pings.png --]
[-- Type: image/png, Size: 10733 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-06-17 10:50 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
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 [this message]
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=874ncxnh82.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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