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 15:09:58 +0000	[thread overview]
Message-ID: <marc-lartc-106139226721744@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106137665106328@msgid-missing>

On Wednesday 20 August 2003 14:58, Raghuveer wrote:
> What is confusing me is, there is a bandwidth provided by ISP (512Kbits)
> and one ethernet capacity(100Mbits), so which one can we call as real
> link bandwidth.  What is NIC bandwidth....is it ethernet bandwidth or
> ISP bandwidth....?
>     Lan------->eth1-----------eth0---------->Internet
> Now at eth0 I have ethernet device bandwidth as 100Mbits and my ISP
> provides 512Kbits bandwidth. so if I want to do egress traffic control
> at both eth0 and eth1, what bandwidth I should consider...? My eth1
> ethernet device bandwidth is 100Mbits.
What bout this :

for all cbq commands : bandwidth 100mbit
eth0
  cbq qdisc
    cbq class rate = 512kbit, bounded
       cbq class 1, rate < 512kbit
       cbq class ..., rate < 512kbit
       cbq class x, rate < 512kbit
So all traffic from class 1 ... x togehter is bounded to 512kbit.  

eth1
  cbq qdisc
    cbq class rate = 100mbit, bounded
       cbq class 1, rate 512kbit bounded
          cbq class 10, rate < 512kbit
          cbq class ..., rate < 512kbit
          cbq class x, rate < 512kbit
       cbq class 2, rate 99,5Mbit
          cbq class 20, rate < 99,5Mbit
          cbq class ..., rate < 99,5Mbit
          cbq class x, rate < 99,5Mbit

Class 1 is for all traffic from internet -> LAN
Class 2 is for all traffic from shaper -> LAN

And if you really want to be sure it's working, you should take 500kbit.  So 
YOU are the bottleneck and in control of the link and not the modem.

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/

  parent reply	other threads:[~2003-08-20 15:09 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
2003-08-20 12:57 ` Raghuveer
2003-08-20 15:09 ` Stef Coene [this message]
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-106139226721744@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.