From: "Cireasa Claudiu" <mozo@home.ro>
To: lartc@vger.kernel.org
Subject: [LARTC] Burst problem!
Date: Wed, 03 Nov 2004 17:17:22 +0000 [thread overview]
Message-ID: <001c01c4c1c8$fcb5cf50$050b010a@mozocomp> (raw)
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
Hello!
I have a problem with i detalied in an early mail but there was no answer so i will try to be more specific.
i have this
tc class add dev eth0 parent 1: classid 1:1 htb rate 64kbit ceil 256kbit burst 15k quantum 1500
tc class add dev eth0 parent 1:1 classid 1:100 htb rate 32kbit ceil 256kbit burst 15k
tc qdisc add dev eth0 parent 1:100 handle 100: sfq perturb 5 quantum 1500
tc class add dev eth0 parent 1:100 classid 1:1001 htb rate 8kbit ceil 64kbit prio 5 quantum 1500 burst 15k
tc qdisc add dev eth0 parent 1:1001 handle 1001: sfq perturb 5 quantum 1500
when i add more clients for the class 1:100 and i start the script problems such as request timeout and verry slow speed (0,5kbps) appear
where is the problem... ? is the burst too big? how should it be set?
the perturb is too small?
i used SFQ... each queue should have her turn once in a while... if i send 10 ping requests from a host at least 2 of them are timeouts... why?
i am stuck please help.
Claudiu.
[-- Attachment #2: Type: text/html, Size: 1977 bytes --]
reply other threads:[~2004-11-03 17:17 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='001c01c4c1c8$fcb5cf50$050b010a@mozocomp' \
--to=mozo@home.ro \
--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.