All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB MPU
Date: Fri, 28 May 2004 19:18:08 +0000	[thread overview]
Message-ID: <200405281518.08108.jasonb@edseek.com> (raw)
In-Reply-To: <40A37E1B.8060604@dsl.pipex.com>

On Friday 28 May 2004 14:54, Andy Furniss wrote:
<snip>
> Reading your other post I see your small traffic is ~100b - this would
> use three cells, so as a temporary kludge you could set your mpu to 159
> and see how it goes.
>
> AFAIK the author of the HTB patch is looking into modifying it to do the
> sums properly for DSL. There isn't one answer though - Eds' formula is
> fine doing the cells bit, but before this you need to add a ppp overhead
> to the IP packet length and this varies with pppoa+vc mux/pppoe/bridged
> pppoe and probably other varieties of dsl implementations.

But there's no tried and true method of determining that information?

You mention at least three methods of mangling PPP with Ethernet/ATM.  And the 
overhead of each kind of setup also would vary depending on the specifics of 
that setup?  (i.e., knowing you have bridged PPPoE doesn't instantly qualify 
you as having an overhread of 123i.)

Sounds particularly complicated.

But the overhead would be a fixed cost, no?  If that is the case you can play 
whack-a-mole with that until you find a 'good' number.  But, as I see it, 
without a realtime ATM cost scheduler, even if I figure out my true 
'overhead' it won't make much difference.

Thoughts, anyone?

> Andy.
>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-05-28 19:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 13:54 [LARTC] HTB MPU Andy Furniss
2004-05-13 14:38 ` Andreas Klauer
2004-05-13 17:28 ` Andreas Klauer
2004-05-13 21:59 ` Jason Boxman
2004-05-14  7:05 ` Ed Wildgoose
2004-05-14  8:40 ` Andy Furniss
2004-05-14  9:55 ` Andy Furniss
2004-05-14 17:10 ` Jason Boxman
2004-05-17 22:36 ` Andy Furniss
2004-05-17 23:33 ` Andy Furniss
2004-05-20  6:29 ` Jason Boxman
2004-05-20 11:13 ` Andy Furniss
2004-05-21  8:19 ` syrius.ml
2004-05-24 20:53 ` Jason Boxman
2004-05-24 23:42 ` Ed Wildgoose
2004-05-28 18:54 ` Andy Furniss
2004-05-28 19:18 ` Jason Boxman [this message]
2004-05-28 21:49 ` Ed Wildgoose
2004-05-30  7:40 ` Andy Furniss
2004-05-30  7:49 ` 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=200405281518.08108.jasonb@edseek.com \
    --to=jasonb@edseek.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.