From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Htb queueing problem
Date: Wed, 01 Mar 2006 20:16:08 +0000 [thread overview]
Message-ID: <44060108.1090000@dsl.pipex.com> (raw)
In-Reply-To: <44043A85.6080302@gmail.com>
Andreas Hasenack wrote:
> On Wed, Mar 01, 2006 at 02:48:18PM +0000, Andy Furniss wrote:
>
>>than bulk. Also remember when setting rates that htb will see ip packets
>>as ip length + 14 when used on ethX
>
>
> Could you elaborate on this a bit?
> I suppose you also meant this in an earlier message when you mentioned
> that the overhead was not included in the bw calculations.
Maybe maybe not - There are even more overheads than 14 on eth and I may
also have meant dsl overheads which you need to allow for using patches
because everything gets padded out to a whole number of ATM cells.
As for the IP length + 14, it's because htb uses skb->len and on eth
thats ip+14 on ppp it's just ip length - I don't know about other
interfaces, you can use HTBs counters to test it.
For eth I often see people use 10 or 100mbit as ceils without adding
overheads to HTB - which you can (38-14$ I suppose), but even then in
practice you need to ceil at slightly less than 10/100mbit.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-03-01 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 11:56 [LARTC] Htb queueing problem Diego Andrés Asenjo Gonzalez
2006-03-01 14:48 ` Andy Furniss
2006-03-01 17:39 ` Diego Andrés Asenjo Gonzalez
2006-03-01 19:07 ` Andreas Hasenack
2006-03-01 19:56 ` Andy Furniss
2006-03-01 20:16 ` Andy Furniss [this message]
2006-03-02 3:56 ` Diego Andrés Asenjo Gonzalez
2006-03-02 15:59 ` Andy Furniss
2006-03-02 16:20 ` m.innocenti
2006-03-02 16:56 ` Luciano Ruete
2006-03-02 18:27 ` Diego Andrés Asenjo Gonzalez
2006-04-11 14:24 ` Edwin Whitelaw
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=44060108.1090000@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.