From: Lawrence MacIntyre <lpz@ornl.gov>
To: lartc@vger.kernel.org
Subject: [LARTC] HFSC
Date: Wed, 12 May 2004 16:36:28 +0000 [thread overview]
Message-ID: <40A2528C.3030306@ornl.gov> (raw)
In-Reply-To: <marc-lartc-98548596122489@msgid-missing>
Hi:
I am using a machine with the 2.4.26 kernel, and trying to compare the
performance of the HTB qdisc with the HFSC one. I have the following
simple script that allows me to have a video stream on port 1234 while
it limits a ttcp UDP stream so that the video stream is unimpaired.
#!/bin/bash
tc qdisc add dev eth0 root handle 1: htb default 12
tc class add dev eth0 parent 1: classid 1:1 htb rate 30mbit ceil 30mbit
tc class add dev eth0 parent 1:1 classid 1:10 htb rate 20mbit ceil 30mbit
tc class add dev eth0 parent 1:1 classid 1:11 htb rate 10mbit ceil 30mbit
tc qdisc add dev eth0 parent 1:10 handle 20: pfifo limit 5
tc qdisc add dev eth0 parent 1:11 handle 30: pfifo limit 5
tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip dport
1234 0xffff flowid 1:10
tc filter add dev eth0 protocol ip parent 1:0 prio 1 u32 match ip dport
5001 0xffff flowid 1:11
Now I would like to try H-FSC. I'm not sure exactly how to go about
this. I thought that creating a ul class with two ls classes inside and
then putting an rt class in one of the ls classes for the video might
work, but I can't seem to get it to work. For example,
#!/bin/bash
/usr/local/bin/tc qdisc add dev eth0 root handle 1: hfsc
/usr/local/bin/tc class add dev eth0 parent 1: classid 1:1 hfsc ul m1
30mbit d 0 m2 30mbit ls m1 30mbit d 0 m2 30mbit
When the second command is executed, the machine simply drops all
packets going through it. I would like to try the 2.6 kernel, but my
machine has an Adaptec SCSI controller that has a broken driver for the
2.6 kernel.
I don't understand why this statement causes the machine to drop all
packets on the eth0 interface.
--
Lawrence MacIntyre 865.574.8696 lpz@ornl.gov
Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-05-12 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-25 2:14 [LARTC] HFSC Rick Goh
2004-02-26 2:39 ` syrius.ml
2004-02-26 13:39 ` Patrick McHardy
2004-02-28 2:59 ` syrius.ml
2004-02-28 6:22 ` Patrick McHardy
2004-02-28 6:42 ` Patrick McHardy
2004-05-12 16:36 ` Lawrence MacIntyre [this message]
2004-05-13 13:05 ` Patrick McHardy
2004-05-13 13:52 ` Lawrence MacIntyre
2004-05-13 14:23 ` Patrick McHardy
2004-05-13 17:43 ` Lawrence MacIntyre
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=40A2528C.3030306@ornl.gov \
--to=lpz@ornl.gov \
--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