All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: Re[2]: [LARTC] CBQ Traffic control not working
Date: Wed, 12 Mar 2003 22:10:28 +0000	[thread overview]
Message-ID: <marc-lartc-104750710530033@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104750472426849@msgid-missing>

On Wednesday 12 March 2003 22:28, Mugur TOMITA wrote:
> Stef Coene, thank you for your feed-back. I have already read
> docum.org... The tests proved a difference of max 20Kbps between
> theory and real life for cbq.
That's because cbq has to guess the conditions on the link and it uses some 
averages.  Like packet size.

> In my case practically nobody is limited...
> In my scripts there are classes with prio 8... you say max is 7...
> could this be the problem?
No.  If you do 
tc -s -d class show dev eth0 
you propably see prio 7 for the prio 8 classes.

> Could it be possible that on hard traffic cbq to just let pass
> packets? This is a stupid question I guess...
> Do I have a chance solving the problem by swtching to HTB?
Yes and no :)
htb is easier to understand/implement, there are no obscure options.  But if 
your problem is setup related, reimplementing the rules in htb can create the 
same problem.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

      reply	other threads:[~2003-03-12 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 21:28 Re[2]: [LARTC] CBQ Traffic control not working Mugur TOMITA
2003-03-12 22:10 ` Stef Coene [this message]

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-104750710530033@msgid-missing \
    --to=stef.coene@docum.org \
    --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.