From: Sorin Panca <sorin.panca@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] counter-strike
Date: Thu, 02 Mar 2006 18:17:43 +0000 [thread overview]
Message-ID: <440736C7.6020507@gmail.com> (raw)
In-Reply-To: <4406DABD.8050700@gmail.com>
Jakub Wartak wrote:
>You should use PRIO to divide traffic into 2 classes
>1) ultra-critical ( here : cs game )
>2) other
>3) very low prio
>
>( more info is on www.voip-info.org , section : QoS under Linux )
>you just have to mark CS packets and put them into the right PRIO class
>
>
>
Class 1:1 has prio 0 in htb and filters. other classes have a higher
priority.
I've made a test. I've added
1: ---- 1:1 --- 10:
htb class sfq
and bloked all other ports and traffic. With this setup I was unable to
lower the ping to be less than 280.
This made me come to the conclusion that ANY_ classification would
introduce a packet delay.
So if I use prio qdisc wouldn't that be a classification?
This is why I created the CS class as a root class.
To answer to the other mail:
CS maximum bandwidth consumption is about 500k. That is why the sum
never exeeds the netrate.
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.
_______________________________________________
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:17 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 [this message]
2006-03-02 18:53 ` Andreas Klauer
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=440736C7.6020507@gmail.com \
--to=sorin.panca@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox