All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] counter-strike
Date: Thu, 02 Mar 2006 15:07:44 +0000	[thread overview]
Message-ID: <20060302150744.GA12637@EIS> (raw)
In-Reply-To: <4406DABD.8050700@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 2411 bytes --]

On Thu, Mar 02, 2006 at 01:45:01PM +0200, Sorin Panca wrote:
> _______________________________________________________________________
> 
> 
> 1:--+----1:1       - [ counter-strike & icmp ] rate=1Mbit; ceil=1Mbit;
>     |                                     prio 0; (u32 filter by ports)
>     |
>     |----1:2       - [ Internet ] rate=1.5Mbit; ceil=rate; prio 1;
>     |     |                       (RNR=rate) RNR = Root iNet Rate
>     |     |
>     |     |---1:20 - [ normal traffic ] rate% of $RNR; ceil=$RNR;
>     |     |                             prio 0; (u32 filter by ports)
>     |     |
>     |     \---1:21 - [ p2p traffic ] (default class) rate=1kbit;
>     |                                ceil% of $RNR; prio 1
>     |
>     |----1:3       - [ MAN ] rate=1Mbit; ceil\x10Mbit-$RNR; prio 1
>     |     |                  (RMCÎil) RMC = Root MAN Ceil
>     |     |                  MAN destinations are marked with 0x1 Marker
>     |     |
>     |     |---1:30 - [ normal traffic ]
>     |     |                    rateP0kbit;ceil=($RMC-$RNR-1)kbit;
>     |     |                    prio 0; (u32 filter by ports AND fw mark)
>     |     |
>     |     \---1:31 - [ p2p traffic ] rate=1kbit; ceil=($RMC-$RNR-1)kbit;
>     |                                prio 1; (u32 filter by fw mark)
>     |
>     \----1:4       - [ LAN ] rate‰Mbit; ceil‰Mbit
> 
> ________________________________________________________________________

I assume that CS actually goes out to Internet and/or MAN, depending on 
the location of the server. I would make one CS class for each. Otherwise 
you may have 1MBit CS (which goes out to Internet) plus 1.5MBit Internet, 
which will work only if you got 2.5MBit Internet guaranteed in total. 
Likewise with MAN. Unless you really got that much bandwidth, this setup 
will not give you any good results at all.

You could also use PRIO qdisc as a child to the HTB Internet / MAN classes 
to give CS absolute priority over HTTP over P2P. This approach worked very 
well for me and my flatmates, also for gaming. But that's on a way slower 
line and without Internet/MAN distinction, so we've been happy with 200ms 
(versus 1000-5000ms when unshaped) pings.

Regards
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-03-02 15:07 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 [this message]
2006-03-02 18:17 ` Sorin Panca
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=20060302150744.GA12637@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.