All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB, MPU, and suitable values
Date: Mon, 17 May 2004 21:23:09 +0000	[thread overview]
Message-ID: <40A92D3D.7020007@wildgooses.com> (raw)
In-Reply-To: <200405171634.02092.jasonb@edseek.com>


>I imagine that 106 value is a reference to this post:
>
>http://mailman.ds9a.nl/pipermail/lartc/2004q2/012369.html
>  
>
...


>It's my suspicion that the MPU and overhead options for HTB would assist in 
>resolving this and enable me to resume using 190kbit instead of 160kbit for 
>the outer most parent class.
>
>Is my suspicion correct?
>  
>

Read the follows to that post as well.  Basically it's only an 
approximation.  The "MPU" is basically pointing out that your ADSL 
stream is encapsulated in an ATM stream.  ATM uses fixed size 64 byte 
packets.  You need at least 2 of these, hence the 108 figure for MPU.  
Now you also need to estimate overhead which is going to be the size of 
the header on those ATM packets. 

However, that still leaves the "wasted space" on the end of small 
packets (eg those that take up 2.5 ATM cells, how much does the 0.5 take 
up).

I suggested a crude way to tweak that patch (easy to see how it works if 
you look at the relevant lines in the orig file). However, I dont even 
have a working QOS system so I haven't even compiled it!  Look up the 
specs for ATM though and you should be able to tweak that suggested line 
change and get something. 

I for one would be really interested to hear if it solves the problem!

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

  reply	other threads:[~2004-05-17 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 20:34 [LARTC] HTB, MPU, and suitable values Jason Boxman
2004-05-17 21:23 ` Ed Wildgoose [this message]
2004-05-17 22:04 ` Jason Boxman
2004-05-18  6:38 ` Ed Wildgoose
2004-05-25 19:48 ` Andreas Klauer
2004-05-25 21:35 ` Ed Wildgoose

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=40A92D3D.7020007@wildgooses.com \
    --to=lists@wildgooses.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.