All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ_bandwidth
Date: Wed, 20 Aug 2003 12:22:03 +0000	[thread overview]
Message-ID: <marc-lartc-106138226211134@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106137665106328@msgid-missing>

On Wednesday 20 August 2003 12:50, Raghuveer wrote:
> Hi Stef,
>
> Reffering to page < http://www.docum.org/stef.coene/qos/faq/cache/7.html
>
>  > I found a para as follows,
>
> " CBQ is not always as accurate as it should be. See docum.org on the
> test page for some tests with bounded classes. The algorithm used by cbq
> is very "link sensitive". It calculates the link idle time and for that
> it needs the real link bandwidth, average packet size and some other
> parameters. But there calculations are not always accurate. So it's
> possible that you will get inaccurate results if you use CBQ to limit
> the traffic in a class.  "
>
> Here Iam slightly confused with real link bandwidth, Can I understand
> that while creating CBQ we need interface bandwidth (ethtool, mii-diag)
> and and while assigning the classes real link bandwidth is required. An
> example will definately help me. Can you pls suggest a way to find real
> link bandwidth....? As ethtool and mii-diag will only get the interface
> bandwidth.
The bandwidth parameter is the real link bandwidth like ethtook or mii-diag 
will show you.
If you want to limit all traffic to the link bandwidth, you have to create a 
class that's bounded and with rate = link bandwidth.  You can create 
non-bounded sub classes but the bandwidth will be limit by the bounded class 
to the link bandwidth.

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-08-20 12:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20 10:50 [LARTC] CBQ_bandwidth Raghuveer
2003-08-20 12:22 ` Stef Coene [this message]
2003-08-20 12:57 ` Raghuveer
2003-08-20 15:09 ` Stef Coene
2003-08-21  4:57 ` Raghuveer
2003-08-21 18:20 ` Stef Coene
2003-08-22  5:29 ` Raghuveer
2003-08-22  8:36 ` Stef Coene
2003-08-22  9:22 ` Raghuveer
2003-08-22 11:39 ` Stef Coene

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-106138226211134@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.