From: Amit Kucheria <amitk@ittc.ku.edu>
To: lartc@vger.kernel.org
Subject: [LARTC] scheduler testing
Date: Fri, 07 Dec 2001 09:46:19 +0000 [thread overview]
Message-ID: <marc-lartc-100771844732631@msgid-missing> (raw)
Hi all,
I am currently trying to test the schedulers available in Linux - CBQ,
FIFO, PRIO, SFQ and WRR.
My setup is simple -
Source --------- Router --------- Sink
eth0 eth1
- The links are 10 Mbit links.
- I am generating average traffic of 1Mbps at the source
- I have to throttle/rate-limit the router-sink link to 1Mbps to make it
look similar to a T1 link to the internet.
- 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.
- I hope to cause queueing due to the statistical nature of traffic
(TCP,UDP) so that instantaneous source thruput might be greater than
1Mbit/s.
I thought of using a TBF class inside a CBQ root qdisc to rate-limit
traffic, but that would drop extra traffic which would prevent queuing.
I would like ideas on how to create queuing assuming that the outgoing
link is like a T1 link. Also what kinds of traffic can i use to simulate
real life situations?
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/2.4Routing/
next reply other threads:[~2001-12-07 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 9:46 Amit Kucheria [this message]
2001-12-07 10:37 ` [LARTC] scheduler testing bert hubert
2001-12-08 22:00 ` Amit Kucheria
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-100771844732631@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.