All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB ATM MPU OVERHEAD (without any patching)
Date: Tue, 12 Apr 2005 19:21:10 +0000	[thread overview]
Message-ID: <425C1FA6.6050004@dsl.pipex.com> (raw)
In-Reply-To: <001001c53ef2$d4a1d2f0$200fa8c0@DELTA>

Chris Bennett wrote:
> Good recommendation.  I read Jesper's thesis (well, okay, not ALL of 
> it... but the juicy bits) and it looks like the difference between the 
> overhead value that I expected to work (24) and the overhead value that 
> actually worked (50) can be explained by the fact that I neglected to 
> include the overhead incurred by bridged mode over ATM (RFC 2684/1483).
> 
> I would say "now I can sleep peacefully", but I just woke up a couple of 
> hours ago... so I'll go for a run instead ;)

LOL - but unless you add your overhead + enough to cover padding you 
still may be taken down if the packet size is just right.

If you know your overhead now it will be far less wastefull to patch - 
use jesper's and do htb aswell as iproute2.

I have patches which are far uglier and lazier, but do the same thing.

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

  parent reply	other threads:[~2005-04-12 19:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12  0:01 [LARTC] HTB ATM MPU OVERHEAD (without any patching) Chris Bennett
2005-04-12  0:14 ` Jason Boxman
2005-04-12  4:05 ` Chris Bennett
2005-04-12 17:27 ` Chris Bennett
2005-04-12 17:29 ` Andy Furniss
2005-04-12 17:40 ` Chris Bennett
2005-04-12 19:14 ` Chris Bennett
2005-04-12 19:21 ` Andy Furniss [this message]
2005-04-12 22:38 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=425C1FA6.6050004@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 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.