From: Sebastian Moeller <moeller0@gmx.de>
To: Fred Stratton <fredstratton@imap.cc>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] some kernel updates
Date: Fri, 23 Aug 2013 21:49:29 +0200 [thread overview]
Message-ID: <EB9CB1CA-9BFA-4D4E-9F4D-570DCE26868C@gmx.de> (raw)
In-Reply-To: <6665470B-0F21-4383-93F6-3D5E87DDE5F3@imap.cc>
Hi Fred,
On Aug 23, 2013, at 15:02 , Fred Stratton <fredstratton@imap.cc> wrote:
[snipp]
>>
>>>
>>> Thus, in kernels >= 3.9, you would need to change/reduce your tc
>>> "overhead" parameter with -14 bytes (iif you accounted encapsulated
>>> Ethernet header before)
>>
>> That is what I thought before, but my kernel spelunking made me reconsider and switch to not subtract the 14 bytes since as I understand it the kernel actively does not do it if stab is used.
>>
>>>
>>> The "overhead" of stab can be negative, so no problem here, in an "int"
>>> for stab.
>>>
>>>
>>>>> Meaning that
>>>>> some ATM encap overheads simply cannot be configured correctly (as you
>>>>> need to subtract the ethernet header).
>>>>
>>>> Yes, I see, luckily PPPoA and IPoA seem quite rare, and setting the overhead to be larger than it actually is is relatively benign, as it will overestimate packe size.
>
>
> As a point of information, the entire UK uses PPPoA rather than PPPoE, and some hundreds of thousands of users IPoA.
Lucky you! I guess one more reason to switch cerowrt over to stab, since PPPoA with VC/mux just adds 10 bytes of overhead, so if the ethernet would be accounted for already that would mean overhead -4 which HTB can not represent anyway. That said, unlike Jesper, I am not sure that tc stab includes the ethernet header by itself currently. Thanks for you input.
[snipp]
Best
Sebastian
next prev parent reply other threads:[~2013-08-23 19:49 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 18:42 Dave Taht
[not found] ` <56B261F1-2277-457C-9A38-FAB89818288F@gmx.de>
[not found] ` <CAA93jw6ku0OOXzNcAUtK4UL5uc7R2zVAOKo1+Fwzmr7gCH1pzA@mail.gmail.com>
[not found] ` <2148E2EF-A119-4499-BAC1-7E647C53F077@gmx.de>
2013-08-23 0:52 ` Sebastian Moeller
2013-08-23 5:13 ` Dave Taht
2013-08-23 7:27 ` Jesper Dangaard Brouer
2013-08-23 10:15 ` Sebastian Moeller
2013-08-23 11:16 ` Jesper Dangaard Brouer
2013-08-23 12:37 ` Sebastian Moeller
2013-08-23 13:02 ` Fred Stratton
2013-08-23 19:49 ` Sebastian Moeller [this message]
2013-08-23 15:05 ` Jesper Dangaard Brouer
2013-08-23 17:23 ` Toke Høiland-Jørgensen
2013-08-23 20:09 ` Sebastian Moeller
2013-08-23 20:46 ` Toke Høiland-Jørgensen
2013-08-24 20:51 ` Sebastian Moeller
2013-08-23 19:51 ` Sebastian Moeller
2013-08-23 9:16 ` Sebastian Moeller
2013-08-23 19:38 ` Sebastian Moeller
2013-08-23 19:47 ` Dave Taht
2013-08-23 19:56 ` Sebastian Moeller
2013-08-23 20:29 ` Dave Taht
2013-08-24 20:51 ` Sebastian Moeller
2013-08-24 20:51 ` Sebastian Moeller
2013-08-25 9:21 ` Fred Stratton
2013-08-25 10:17 ` Fred Stratton
2013-08-25 13:59 ` Sebastian Moeller
2013-08-25 14:26 ` Fred Stratton
2013-08-25 14:31 ` Fred Stratton
2013-08-25 17:53 ` Sebastian Moeller
2013-08-25 17:55 ` Dave Taht
2013-08-25 18:00 ` Fred Stratton
2013-08-25 18:30 ` Fred Stratton
2013-08-25 18:41 ` Dave Taht
2013-08-25 19:08 ` Fred Stratton
2013-08-25 19:31 ` Fred Stratton
2013-08-25 21:54 ` Sebastian Moeller
2013-08-25 20:28 ` Dave Taht
2013-08-25 21:40 ` Sebastian Moeller
2013-08-25 21:50 ` Sebastian Moeller
2013-08-27 11:10 ` Jesper Dangaard Brouer
2013-08-27 10:45 ` Jesper Dangaard Brouer
2013-08-30 15:46 ` [Cerowrt-devel] some kernel updates + new userspace patch Jesper Dangaard Brouer
2013-08-27 10:42 ` [Cerowrt-devel] some kernel updates Jesper Dangaard Brouer
2013-08-24 23:08 ` Sebastian Moeller
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=EB9CB1CA-9BFA-4D4E-9F4D-570DCE26868C@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=fredstratton@imap.cc \
/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