From: "Thomas Switala" <tis@genotribe.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Qos Slowing down
Date: Wed, 19 Nov 2003 08:02:26 +0000 [thread overview]
Message-ID: <marc-lartc-106923137117513@msgid-missing> (raw)
Hi
I have a bandwidth manager configured on the following system:
RedHat 8.0
Kernel - 2.4.20 (Recompiled and I changed the
SFQ_DEPTH to 512
and the SFQ_HASH 3072
and the PSCHED_CLOCK_SOURCE
= PSCHED_CPU
Patches for the kernel = ebtables
glibc-2.3.2-4.80.6
The system is build to act as a bridge. Qos happens on the outgoing eth0
device to about
175 differant subnets. I am using HTB and I have the following hierachy
Group1
|
-----------------------------------------
|
|
SP1 SP2
|
|
------------- -------------
| | | | | |
| |
cl1 cl2 cl3 cl4 cl5 cl6 cl7 cl8
Al of the cl belong to a service provider (sp) where they are on shared
bandwidth
all of them have a CIR of 1 and a Ceil of 384kbps.
The problem that I am experiencing , and it happens often lately is that the
Qos slows down and
it doesn't pass any traffic at all. I have to restart the whole system
before it starts working again.
If I stop the tc on the device it works as well which rules out the
bridging.
What could be wrong and is Linux going to handle more than 800 sites on a
40Mbps connection ?
--
Warm Regards
Thomas I. Switala
CEO and Lead Systems Architect Genotribe Ltd
--
Cell : +27-82-822-5080 (South-Africa)
+234-803-794-8252 (Nigeria)
IM: genotribe@jabber.genotribe.com (Jabber)
genotribe (Yahoo)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-11-19 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 8:02 Thomas Switala [this message]
2003-11-19 18:27 ` [LARTC] Qos Slowing down Stef Coene
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-106923137117513@msgid-missing \
--to=tis@genotribe.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.