From: "Harkisoon Sharan (CCI-Gainesville)" <Sharan.Harkisoon@cox.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Problem creating a lot of classes
Date: Tue, 20 May 2003 16:31:04 +0000 [thread overview]
Message-ID: <marc-lartc-105344838904699@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105335438307360@msgid-missing>
Thank you Martias. I downloaded Devik's patch, which includes a patched TC binary. Works like a charm.
-----Original Message-----
From: Matias Bjørling [mailto:mb@nerdit.dk]
Sent: Tuesday, May 20, 2003 9:32 AM
To: Harkisoon Sharan (CCI-Gainesville)
Cc: lartc@mailman.ds9a.nl
Subject: Re: [LARTC] Problem creating a lot of classes
Hey
It's a bug in TC, upgrade to a newer version and it should be fixed. I had
the same problem on a dual xeon 2.4 ghz with crashed with 100 classes
loaded. Did'nt understand why...
Regards
Matias Bjørling
----- Original Message -----
From: "Harkisoon Sharan (CCI-Gainesville)" <Sharan.Harkisoon@cox.com>
To: <lartc@mailman.ds9a.nl>
Sent: Monday, May 19, 2003 4:21 PM
Subject: [LARTC] Problem creating a lot of classes
Hello,
I'm looking for a little advice. The following example works great for me
on a small scale test, but I'm trying to implement this on a larger scale
for a /22 address space, where every user is commited 1mbit of bandwidth.
Unfortunately, when I try to create over 600 classes, I get a kernel panic
(the threshold is somewhere between 600-750 for me).
I am using a Dell Poweredge 2450 with 1gig of ram, dual 733mhz, with a
standard Redhat9 install/kernel.
Any suggestions, or alternative configurations would be appreciated.
Thanks,
Sharan Harkisoon
Here's the script:
#!/bin/sh
ingress=eth0
egress=eth1
downstream=1mbit
upstream=1mbit
#clear shaping on interfaces
tc qdisc del dev $egress root
tc qdisc add dev $egress root handle 1: htb default 1
tc class add dev $egress classid 1:1 htb rate $downstream
tc class add dev $egress classid 1:2 htb rate $downstream
tc class add dev $egress classid 1:3 htb rate $downstream
..
#ommitted
..
tc class add dev $egress classid 1:1021htb rate $downstream
tc filter add dev $egress protocol ip prio 1 u32 match ip dst 24.136.40.2
flowid 1:1
tc filter add dev $egress protocol ip prio 1 u32 match ip dst 24.136.40.3
flowid 1:2
tc filter add dev $egress protocol ip prio 1 u32 match ip dst 24.136.40.4
flowid 1:3
..
#ommitted
..
tc filter add dev $egress protocol ip prio 1 u32 match ip dst 24.136.43.254
flowid 1:1021
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-05-20 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 14:21 [LARTC] Problem creating a lot of classes Harkisoon Sharan (CCI-Gainesville)
2003-05-20 13:32 ` Matias Bjørling
2003-05-20 16:31 ` Harkisoon Sharan (CCI-Gainesville) [this message]
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-105344838904699@msgid-missing \
--to=sharan.harkisoon@cox.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.