From: Adam James <ad@heliosphan.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Patch to allow for the ATM "cell tax"
Date: Tue, 14 Mar 2006 02:10:56 +0000 [thread overview]
Message-ID: <20060314021056.6de68b39@heliosphan.kernelpanic.co.uk> (raw)
In-Reply-To: <1141284603.10264.168.camel@ras.pc.brisbane.lube>
On Tue, 14 Mar 2006 11:26:12 +1000
Russell Stuart <russell@stuart.id.au> wrote:
> The complete table, for the _outbound_ direction going
> over an Ethernet link is:
>
> PPPoA + VC/Mux: tc class add htb … overhead -8 atm
> PPPoA + VC/LLC: tc class add htb … overhead 4 atm
> PPPoE + VC/Mux: tc class add htb … overhead 20 atm
> PPPoE + VC/LLC: tc class add htb … overhead 28 atm
>
> The complete table for incoming traffic on the IMQ
> device, regardless of the type of connection, is:
>
> PPPoA + VC/Mux: tc class add htb … overhead 10 atm
> PPPoA + VC/LLC: tc class add htb … overhead 18 atm
> PPPoE + VC/Mux: tc class add htb … overhead 34 atm
> PPPoE + VC/LLC: tc class add htb … overhead 42 atm
Why is the PPPoA VC/Mux overhead for outbound traffic 6 octets and 10
octets for inbound? My interpretation of RFC 2364 is that the AAL5
footer for VC multiplexed PPPoA is 8 octets, meaning a -4 overhead on
incoming traffic.
What am I missing?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-03-14 2:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 7:30 [LARTC] Patch to allow for the ATM "cell tax" Russell Stuart
2006-03-02 13:37 ` Markus Schulz
2006-03-02 13:51 ` Markus Schulz
2006-03-02 15:49 ` Andy Furniss
2006-03-02 19:54 ` Adam James
2006-03-02 21:35 ` Andy Furniss
2006-03-02 22:18 ` Russell Stuart
2006-03-02 22:23 ` Stephen Hemminger
2006-03-02 22:45 ` Jason Boxman
2006-03-02 23:44 ` Russell Stuart
2006-03-03 0:27 ` Jason Boxman
2006-03-03 0:43 ` Russell Stuart
2006-03-03 1:23 ` Markus Schulz
2006-03-03 1:49 ` Markus Schulz
2006-03-03 1:54 ` Russell Stuart
2006-03-03 2:23 ` Markus Schulz
2006-03-03 2:27 ` gentoo
2006-03-03 13:43 ` Andreas Hasenack
2006-03-03 16:18 ` Jason Boxman
2006-03-03 16:45 ` Andreas Hasenack
2006-03-03 18:45 ` Jason Boxman
2006-03-03 19:34 ` Andreas Hasenack
2006-03-05 19:27 ` Andy Furniss
2006-03-06 17:26 ` Jesper Dangaard Brouer
2006-03-13 18:09 ` Jason Boxman
2006-03-14 0:34 ` Russell Stuart
2006-03-14 0:49 ` Jason Boxman
2006-03-14 1:26 ` Russell Stuart
2006-03-14 2:10 ` Adam James [this message]
2006-03-14 13:14 ` Andy Furniss
2006-03-14 13:25 ` Andy Furniss
2006-03-14 23:28 ` Russell Stuart
2006-03-15 0:29 ` Andy Furniss
2006-12-06 18:59 ` Taylor, Grant
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060314021056.6de68b39@heliosphan.kernelpanic.co.uk \
--to=ad@heliosphan.co.uk \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.