From: Andy Furniss <adf.lists@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>,
Alan Goodman <notifications@yescomputersolutions.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
"lartc@vger.kernel.org" <lartc@vger.kernel.org>
Subject: Re: [Cerowrt-devel] Correctly calculating overheads on unknown connections
Date: Tue, 23 Sep 2014 16:10:00 +0100 [thread overview]
Message-ID: <54218D48.1020906@gmail.com> (raw)
In-Reply-To: <A7D5AE57-7B27-448E-B000-FCE649F81D25@gmx.de>
Sebastian Moeller wrote:
> I would just go and account for all overheads I could deduce, so I
> would guess: 8 bytes PPPoE, 4 byte VLAN tags, 14 bytes ethernet
> header (note for tc’s stab method one needs to include the ethernet
> headers in the specified overhead in spite of the man page)
I don't think the man page is wrong - it includes eth in the pppoe example.
There is a difference between shaping on ppp and shaping on eth which
needs to be and is noted.
FWIW I tried a few pings on my VDSL2 and don't think I'll be any use for
results.
I do get an increase with larger packets but it's more than it should be
:-(.
The trouble is that my ISP does DPI/Ellacoya Qos for my ingress and I
guess this affects things a bit too much for sub milisecond accuracy
needed on a 20/80 line.
At least I don't have to bother so much about ingress shaping (not that
I would @80mbit so much anyway).
Ping and game traffic comes in tos marked 0x0a and gets prio on their
egress which is set slightly lower than my sync profile speed.
Additionally it's probably not the best time to test as they had a
recent outage which caused in-balance on their gateways which seems to
still persist.
next prev parent reply other threads:[~2014-09-23 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <541C9527.1070105@yescomputersolutions.com>
[not found] ` <541DA8B5.70701@gmail.com>
2014-09-20 17:55 ` Dave Taht
2014-09-20 22:29 ` Andy Furniss
2014-09-21 18:35 ` Sebastian Moeller
[not found] ` <CAK1m8mPBWyg-sR-ekZGUhsOG-0HoZd3eJ-Q6HJpSLyN-J90kHg@mail.gmail.com>
2014-09-21 21:40 ` Alan Goodman
2014-09-22 9:05 ` Sebastian Moeller
2014-09-22 10:01 ` Andy Furniss
2014-09-22 10:20 ` Sebastian Moeller
2014-09-22 13:09 ` Alan Goodman
2014-09-22 19:52 ` Sebastian Moeller
2014-09-22 23:02 ` Alan Goodman
2014-09-23 9:32 ` Sebastian Moeller
2014-09-23 15:10 ` Andy Furniss [this message]
2014-09-23 17:47 ` Sebastian Moeller
2014-09-23 19:05 ` Andy Furniss
2014-09-23 22:16 ` Sebastian Moeller
2014-09-24 9:17 ` Andy Furniss
2014-09-24 16:23 ` Sebastian Moeller
2014-09-24 22:48 ` Andy Furniss
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=54218D48.1020906@gmail.com \
--to=adf.lists@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=lartc@vger.kernel.org \
--cc=moeller0@gmx.de \
--cc=notifications@yescomputersolutions.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