Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Patch to allow for the ATM "cell tax"
Date: Thu, 02 Mar 2006 21:35:35 +0000	[thread overview]
Message-ID: <44076527.9030402@dsl.pipex.com> (raw)
In-Reply-To: <1141284603.10264.168.camel@ras.pc.brisbane.lube>

Adam James wrote:

> As Markus mentioned in another post on this thread, Jesper Dangaard
> Brouer (http://www.adsl-optimizer.dk) has already written an iproute2
> and Linux kernel patch that implements the above. ATM cell alignment is
> done in tc_core.c, and the per packet overhead is passed to the relevant
> kernel modules.
> 
> I have made some very minor changes to the patches, so that they apply
> cleanly to iproute2-20051007 and kernel 2.6.15. You will find them
> attached to this mail.

Just remember to take 14 from your overhead if your modem is connected 
via eth rather than ppp etc. This means you need to put a negative 
overhead (can you?) if using pppoa/vcmux


> Setting the MTU to 1478 is probably a good idea to prevent excessive
> cell usage. Reasoning behind this being: 1488 is the largest multiple of
> 48 under 1500, less 2 bytes for the PPP header and 8 for the AAL5
> footer.
> 
> Perhaps you can confirm this isn't way off the mark Andy? :)

1478 is optimal if your overhead is 10 - I use it.

For the pppoes I don't think you gain much as you loose tcp data 
efficiency by using smaller packets.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-03-02 21:35 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 [this message]
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
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=44076527.9030402@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox