From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] counter-strike
Date: Thu, 02 Mar 2006 18:53:49 +0000 [thread overview]
Message-ID: <20060302185349.GA14603@EIS> (raw)
In-Reply-To: <4406DABD.8050700@gmail.com>
On Thu, Mar 02, 2006 at 08:17:43PM +0200, Sorin Panca wrote:
> I've made a test. I've added
> 1: ---- 1:1 --- 10:
> htb class sfq
If that SFQ is the standard sfq with a queuelength of 128 packets,
it might be responsible for some of the delay. Unless you have
connections in there that can choke the whole bandwidth (probably
possible with CS if you set the rates up, I don't know), you may
not need SFQ for interactive bands at all.
> People in my LAN play almost exclusively in MAN, not in the Internet. I
> allocated such high bandwidth because htb would allocate the spare based
> on classes' rates ratios. And since 1:1 is a root class as 1:2 and 1:3
> (MAN and Internet respectively) it had to have such a rate even if it is
> not found in my real bandwidth.
I don't think I follow your explanation here. How do you expect HTB to
guarantee a rate for a class (that's what it claims to do) when there
is no bandwidth to back it up.
I've never dealt with MANs before, so I may be completely wrong.
Usually you should not have more than one root class, and you should
not let HTB think it can use more bandwidth than there actually is.
It's extremely hard to understand the logic behind setups like this
and therefore likely to get unexpected results from them.
Regards
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-03-02 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 11:45 [LARTC] counter-strike Sorin Panca
2006-03-02 14:23 ` Jakub Wartak
2006-03-02 15:07 ` Andreas Klauer
2006-03-02 18:17 ` Sorin Panca
2006-03-02 18:53 ` Andreas Klauer [this message]
2006-03-02 20:13 ` Sorin Panca
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=20060302185349.GA14603@EIS \
--to=andreas.klauer@metamorpher.de \
--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.