From: Poop <zoop@lendingfirst.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Question about qdisc and class
Date: Mon, 17 Jun 2002 20:49:18 +0000 [thread overview]
Message-ID: <marc-lartc-102434709313464@msgid-missing> (raw)
I have a question about the difference between a qdisc and a class and a
classid and a flowid, I am reading the HOWTO but I am a little confused
about this.
I see lines like this:
tc filter add dev eth1 parent 1:0 protocol ip prio 100 match ip src \
1.2.0.0 classid 1:1
Then I see one like this
tc filter add dev eth1 protocol ip parent 1:0 prio 5 u32 ht 2:7b: \
match ip src 1.2.0.123 flowid 1:1
I do notice there is a difference I'm just not sure why you use classid
in one and flowid in the other.
I also see stuff like this
tc qdisc add dev eth0 root handle 1: htb default 30
tc class add dev eth0 parent 1: classid 1:1 htb rate 5mbit burst 15k
and I'm not sure why the command changed from qdisc to class.
If there is more documentation some where could you point me to it or
let me know what the differences are here.
Thank you all for your time.
Zoop
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-06-17 20:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-102434709313464@msgid-missing \
--to=zoop@lendingfirst.com \
--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.