From: Amit Kucheria <amitk@ittc.ku.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] scheduler testing
Date: Sat, 08 Dec 2001 22:00:24 +0000 [thread overview]
Message-ID: <marc-lartc-100784888629125@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100771844732631@msgid-missing>
On Fri, 7 Dec 2001, Amit Kucheria wrote:
Hi all,
I am currently trying to test the schedulers available in Linux - CBQ,
FIFO, PRIO, SFQ and WRR.
My setup is simple -
10Mbit 10Mbit
Source --------- Router --------- Sink
eth0 eth1
- I need to simulate the 'router-sink' link at a T1 link. obviously the
best way to do this is to but a TBF on eth1.
But i want to test various kinds of queueing disciplines with this rate
limited traffic. This wont be allowed by TBF which cant take classes.
So would the following work ?
1Mbit
TBF qdisc 2:0 +--------+ ******* My various classes FIFO, CBQ
CBQ class 1:1 +----------+ +--------+ CBQ class 1:2
+-------------------------+ CBQ qdisc 1:0
Now TBF rate limits to 1Mbit and then a filter filters the packet to "my
various classes which could be multiple CBQ, prio classes or simple fifo.
- I am generating average traffic of 1Mbps at the source
- I need a rate-limiting architecture which will allow be to test various
schedulers as well as impose a strict limit on the outgoing link.
Regards,
Amit
--
The statement below is true.
The statement above is false.
^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^
Amit Kucheria
EECS Grad. Research Assistant
University of Kansas @ Lawrence
(R)+1-(785)-830 8521 ||| (O)+1-(785)-864 7774
____________________________________________________
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2001-12-08 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 9:46 [LARTC] scheduler testing Amit Kucheria
2001-12-07 10:37 ` bert hubert
2001-12-08 22:00 ` Amit Kucheria [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-100784888629125@msgid-missing \
--to=amitk@ittc.ku.edu \
--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.