Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Alberto Bertogli <albertogli@altavista.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ and all other qdiscs now REALLY completely documented (almost!)
Date: Mon, 03 Dec 2001 02:45:57 +0000	[thread overview]
Message-ID: <marc-lartc-100742087601258@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100734471005654@msgid-missing>

On Mon, Dec 03, 2001 at 03:32:15AM +0100, bert hubert wrote:
> On Sun, Dec 02, 2001 at 11:16:49PM -0300, Alberto Bertogli wrote:
> 
> > The comment, still present today (of course =) is:
> > 
> >         Note that the peak rate TBF is much more tough: with MTU 1500
> >         P_crit = 150Kbytes/sec. So, if you need greater peak
> >         rates, use alpha with HZ\x1000 :-)
> > 
> > Even below in the description, when it describes peakrate parameter, it
> > says "However, due to de default 10ms timer resolution of Unix, with
> > 10.000 bits average packets, we are limited to 1mbit/s of peakrate!"
> 
> 150Kbytes/sec -> 1mbit/s! (more or less). Depends a bit on what your average
> packet size is. 
> 

Yeah I'm just stupid and read everything as bps. Luckly i forgot to CC to
the list =)


> SFQ doesn't shape, so it's a whole different ballgame. 

Yeah, I shape with CBQ anyway.. what reminds me to my next question: is
HTB going to be merged in 2.4? is it ready for production use?


Thanks,
		Alberto


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

  parent reply	other threads:[~2001-12-03  2:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03  1:58 [LARTC] CBQ and all other qdiscs now REALLY completely documented (almost!) bert hubert
2001-12-03  2:26 ` Jim Fleming
2001-12-03  2:45 ` Alberto Bertogli [this message]
2001-12-03  2:53 ` bert hubert

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=marc-lartc-100742087601258@msgid-missing \
    --to=albertogli@altavista.net \
    --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