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] HTB and PRIO qdiscs introducing extra	latency	when	output
Date: Wed, 19 Oct 2005 10:59:46 +0000	[thread overview]
Message-ID: <43562722.9050106@dsl.pipex.com> (raw)
In-Reply-To: <1122460110.8454.11.camel@pgala.it.nuigalway.ie>

Andy Furniss wrote:
> Andy Furniss wrote:
> 
>> I haven't checked those figures or tested close to limits though, the 
>> 12k burst would need increasing a bit aswell or that will slightly 
>> over limit rate at HZ\x1000.
> 
> 
> It seems that htb still uses ip level for burst so 12k is enough.
> 
> With the overhead at 38 I can ceil at 99mbit OK.
> 

Jonathan spotted that on eth skb->len is ip len + 14 so overhead should 
be 24 not 38.

Andy.


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

  parent reply	other threads:[~2005-10-19 10:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27 10:28 [LARTC] HTB and PRIO qdiscs introducing extra latency when Jonathan Lynch
2005-07-27 13:25 ` [LARTC] HTB and PRIO qdiscs introducing extra latency when output Andy Furniss
2005-07-27 15:37 ` Jonathan Lynch
2005-07-27 21:53 ` Andy Furniss
2005-07-28 16:37 ` Jonathan Lynch
2005-07-28 21:49 ` Andy Furniss
2005-08-02 20:59 ` Jonathan Lynch
2005-08-03 14:04 ` Andy Furniss
2005-08-03 19:32 ` Andy Furniss
2005-08-04 18:06 ` Andy Furniss
2005-10-19 10:59 ` Andy Furniss [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-10 18:37 Jonathan Lynch
2005-08-11 16:36 ` Andy Furniss
2005-08-20 20:51 Jonathan Lynch

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=43562722.9050106@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