From: Dimitris Zilaskos <dzila@tassadar.physics.auth.gr>
To: lartc@vger.kernel.org
Subject: [LARTC] tc reliably hangs my system
Date: Wed, 03 Jul 2002 16:33:25 +0000 [thread overview]
Message-ID: <marc-lartc-102571407326905@msgid-missing> (raw)
kernel 2.4.18-ac3 smp , iproute2-2.4.7-now-ss020116-try.tar.gz
I am using the following scripts to adjust my traffic during certain
periods of time , running them cron and sometimes by hand . They can
reliably freeze the system if they are run certain number of times .
No oops/panic/errors of whatsoever , just a frozen system .
the following "fast" script freezes the system after it is executed 7-8
times
tc qdisc del dev eth0 root
tc qdisc add dev eth0 root handle 10: cbq bandwidth 100Mbit avpkt 1000
tc class add dev eth0 parent 10:0 classid 10:1 cbq bandwidth 100Mbit \
rate 100Mbit allot 1514 weight 10Mbit prio 8 maxburst 20 avpkt 1000
tc class add dev eth0 parent 10:1 classid 10:100 cbq bandwidth 100Mbit \
rate 100Mbit allot 1514 weight 10Mbit prio 5 maxburst 20 avpkt 1000
tc class add dev eth0 parent 10:1 classid 10:200 cbq bandwidth 100Mbit \
rate 100Mbit allot 1514 weight 10Mbit prio 5 maxburst 20 avpkt 1000
tc qdisc add dev eth0 parent 10:100 sfq quantum 1514b perturb 10
tc qdisc add dev eth0 parent 10:200 tbf rate 6Mbit latency 50ms burst \
50000
tc qdisc del dev eth0 ingress
tc qdisc add dev eth0 handle ffff: ingress
tc filter add dev eth0 parent ffff: protocol ip prio 2 u32 match ip \
protocol 1 0xFF police rate 1kbit burst 10000 mtu 1k drop flowid :1
tc filter add dev eth0 parent 10: protocol ip prio 1 u32 match ip dst \
1.2.3.0/16 flowid 10:100
tc filter add dev eth0 parent 10: protocol ip prio 1 u32 match tcp src \
22 0xffff match ip protocol 0x6 0xff flowid 10:100
tc filter add dev eth0 parent 10: protocol ip prio 1 u32 match ip src \
1.2.3.25/32 flowid 10:200
The following "slow" script freezes the system after being executed
around 11-18 times
tc qdisc del dev eth0 root
tc qdisc add dev eth0 root handle 10: cbq bandwidth 100Mbit avpkt 1000
tc class add dev eth0 parent 10:0 classid 10:1 cbq bandwidth 100Mbit \
rate 100Mbit allot 1514 weight 10Mbit prio 8 maxburst 20 avpkt 1000
tc class add dev eth0 parent 10:1 classid 10:100 cbq bandwidth 100Mbit \
rate 100Mbit allot 1514 weight 10Mbit prio 5 maxburst 20 avpkt 1000
tc class add dev eth0 parent 10:1 classid 10:200 cbq bandwidth 100Mbit \
rate 100Mbit allot 1514 weight 10Mbit prio 5 maxburst 20 avpkt 1000
tc qdisc add dev eth0 parent 10:100 sfq quantum 1514b perturb 10
tc qdisc add dev eth0 parent 10:200 tbf rate 3Mbit latency 50ms burst \
50000
tc qdisc del dev eth0 ingress
tc qdisc add dev eth0 handle ffff: ingress
tc filter add dev eth0 parent ffff: protocol ip prio 2 u32 match ip \
protocol 1 0xFF police rate 1kbit burst 10000 mtu 1k drop flowid :1
tc filter add dev eth0 parent 10: protocol ip prio 1 u32 match ip dst \
1.2.3.0/16 flowid 10:100
tc filter add dev eth0 parent 10: protocol ip prio 1 u32 match tcp src \
22 0xffff match ip protocol 0x6 0xff flowid 10:100
tc filter add dev eth0 parent 10: protocol ip prio 1 u32 match ip src \
1.2.3.25/32 flowid 10:200
The ingress related parts are the prime suspects for me , i added them
recently . Before that no freezing has ever ocurred . I couldn't perform
more tests because the box is a rather busy server and the lockups cause
painfull reboots .
Any advice is welcomed .
Kind regards ,
--
======================================
Dimitris Zilaskos
Department of Physics @ Aristotle Univercity of Thessaloniki , Greece
======================================
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-07-03 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 16:33 Dimitris Zilaskos [this message]
2002-07-03 16:47 ` [LARTC] tc reliably hangs my system Stef Coene
2002-07-04 8:07 ` Dimitris Zilaskos
2002-07-04 10:07 ` Dimitris Zilaskos
2002-07-04 14:42 ` bert hubert
2002-07-04 18:24 ` bert hubert
2002-07-05 13:35 ` Dimitris Zilaskos
2002-07-05 14:59 ` bert hubert
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-102571407326905@msgid-missing \
--to=dzila@tassadar.physics.auth.gr \
--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.