Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Ethloop?
Date: Fri, 07 Jun 2002 18:45:10 +0000	[thread overview]
Message-ID: <marc-lartc-102347559013624@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102340461224067@msgid-missing>

You either missed "ceil" parameter or it is missing on my page :)
Without ceil it is the same as rate thus all classes are bounded
in fact. Add ceil 100kbps to each line.
devik

On Fri, 7 Jun 2002, King Yung Tong wrote:

> Thank you for your reply :)
> I try to follow chapter 6 on your user guide.
>
> 		1:1
> 	      /     \
>  	    1:2     1:12
>            /   \
>          1:10   1:11
>         (prio1) (prio2)
>
> If 1:12 don't have any traffic, all the BW on 1:12 can be assigned to 1:2,
> is that right?
>
> I try to put all these extra (from 1:12) to 1:10, my htb script is as
> follows, and I use ethloop to test and I found that 1:10 will not get the
> extra from 1:12. Could you tell me where I make a mistake? Thank you.
>
> echo Clean all the tc setup
> ./tc qdisc del dev lo root
> ./tc qdisc add dev lo root handle 1: htb default 12
>
> ./tc class add dev lo parent 1: classid 1:1 htb rate 100kbps
> ./tc class add dev lo parent 1:1 classid 1:2 htb rate 40kbps
> ./tc class add dev lo parent 1:2 classid 1:10 htb rate 30kbps prio 0
> ./tc class add dev lo parent 1:2 classid 1:11 htb rate 10kbps prio 1
> ./tc class add dev lo parent 1:1 classid 1:12 htb rate 60kbps
>
> echo qdisc
> ./tc qdisc add dev lo parent 1:10 handle 20: pfifo limit 5
> ./tc qdisc add dev lo parent 1:11 handle 30: pfifo limit 5
> ./tc qdisc add dev lo parent 1:12 handle 40: sfq perturb 10
>
> Input for ethloop:
>
> # lo will be used to TX and RX
> 0       i       0       lo
> 0       i       1       lo
> 0       i       2       lo
> # set simulation packet size to 1k
> 0       S       0       1k
> 0       S       1       1k
> 0       S       2       1k
> # flow 0 AE, flow 1  BE, flow 2 EF
> 0       P       0       0x10010
> 0       P       1       0x10011
> 0       P       2       0x10012
> # start all flow at defined rate
> 0       R       0       30000
> 0       R       1       10000
> 0       R       2       60000
> # Create extra at 1:12 and borrow this to 1:2 <------?
> 5000    R       0       30000
> 5000    R       1       10000
> 5000    R       2       0
> # 1:10 and 1:11 and 1:10 should get higher value <------?
> 15000    R      0       40000
> 15000    R       1      20000
> # finish at 8sec
> 25000    X      0        0
>
> Result is to long, I use gnuplot and found that 1:10 at most get 30000.
>
> Thank you for you help.
>
> Pat
>
>
>
> On Fri, 7 Jun 2002, Martin Devera wrote:
>
> > What is the problem ? use cat ethloop_script|./ethloop
> > for example ..
> > devik
> >
> > On Thu, 6 Jun 2002, King Yung Tong wrote:
> >
>
>
>

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

  parent reply	other threads:[~2002-06-07 18:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 23:02 [LARTC] Ethloop? King Yung Tong
2002-06-07 18:02 ` Martin Devera
2002-06-07 18:36 ` King Yung Tong
2002-06-07 18:45 ` Martin Devera [this message]
2002-06-07 18:57 ` King Yung Tong
2002-06-07 19:06 ` Martin Devera
2002-06-07 19:47 ` Martin Devera
2002-06-07 19:47 ` King Yung Tong
2002-06-07 19:53 ` King Yung Tong
2002-06-07 20:03 ` Martin Devera
2002-06-07 20:17 ` King Yung Tong
2002-06-07 20:19 ` Martin Devera
2002-06-07 20:26 ` King Yung Tong
2002-06-07 20:48 ` Martin Devera
2002-06-07 20:53 ` King Yung Tong

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-102347559013624@msgid-missing \
    --to=devik@cdi.cz \
    --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