Yes, thats one possibility (without the dummy device though please).
But I wonder what this would actually be useful for. I don't think
replacing the root qdisc by a different type is a common scenario,
for the same type you can simply use "tc qdisc change", "tc class
change" and "tc class replace".
Badalian, what are you actually doing?
Sorry. Resend to all.
I simple recreate all rules. I change idea from do many
add,change,delete because have many kernel panics on many kernels 2.6.x
First i have panics on "delete filter" operation... was fix it...
great.. then have panics on "delete htb" operation... long time wait to
fix it (maintainer of tc not have time to fix it i think).. but have 1-5
panics at day.... i think my clients hate me =) i rewrite script to
simple recreate all rules... in this method i have small packetlost 1
time in hour (then recreate root qdisc), but not have panics... now i
use new logic of scripts... =)
maybe need go back to accurate logic of scripts, but i to fear kernel
panics =)
P.S. Feature request:
tc class show [ dev STRING ] [ root | parent CLASSID ]
may add classid filter to show?
i need do like this
/sbin/tc -s class show dev eth0 | grep -A2 "htb $HTB "
to get stats of class... but i every run real look all table.. its not good
Thanks that are you interesting history of my problems =)
Slavon.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
