From: <mjoachimiak@poczta.onet.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Gamest and QoS
Date: Wed, 18 Aug 2004 08:49:31 +0000 [thread overview]
Message-ID: <000501c48500$4fcaee10$0802a8c0@monster> (raw)
In-Reply-To: <785497368.20040818040336@op.pl>
While using htb have a look at r2q option and quantum (1500 bytes more or
less).
Threre is a special formula for it: quantum=(rate in kilobytes)/r2q it shuld
1500 byte. Try to set r2q to have on this level.Good thing is to have
conn-limit patch from patch-o-matic to limit max connection from one
client - it lowers ping too.
Please do write what did you do and if it helped to resolve the problem.
Good luck.
> > > Without QoS, while uploading some files via ftp i have pings (in my
> > favourite
> > > game) 1000+. With my qos script my ping lower to 150 - 300, but is
> > > very unstable.
> > >
> > > Is there any way to configure htb, to have good, __STABLE__ pings
( 40
> > - 100)
> > > while other people exploring the internet.
>
> I've had this problem for about a year now, I'm not sure what the cause is
> exactly but I think it has to do with the minimum burst size that HTB must
> have, which is something like 1.5kbytes (per class), combined with the
> restricted timers that linux QoS uses. Anyway, what I ended up doing is
using
> the prio qdisc (which doesn't do rate limiting, only prioritises packets)
> wrapped inside a TBF qdisc for its rate limiting. See my script below.
>
> > One question I'd be wondering, is how to filter the game packets into
> > the class. I'm a UT2k4 fan, and it's not as easy as just filtering
> > based on port as the server ports are all over the map. Perhaps one
> > would have to look at the packet size instead. Hopefully it would be
> > constant or small.
>
> One way to filter this that might work, is to just put all the UDP traffic
in
> your interactive class, which I assume UT2k4 uses. Not very many programs
> besides games use UDP traffic for its data transfer, so it should work
> without putting too much unwanted packets into your interactive class. As
> well, if your using ipp2p or port matching your p2p/ftp traffic, they
won't
> be put into the interactive class. It's quite important to put your packet
> marking statements (iptables) in the right order also, if you do it in the
> wrong order all your packets will end up in your interactive class
(happened
> to me in the beginning :) ). My script below should clarify things.
>
> Download my script here:
> http://quebeck.dyndns.org/temp/simple.htb
>
> I haven't finished fine tuning it yet, but the basic traffic shaping
works.
>
> Jon
>
> Find local movie times and trailers on Yahoo! Movies.
> http://au.movies.yahoo.com
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-08-18 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 2:03 [LARTC] Gamest and QoS Marcin Sura
2004-08-18 5:53 ` Trevor Cordes
2004-08-18 7:38 ` Jonathan Soh
2004-08-18 8:49 ` mjoachimiak [this message]
2004-08-20 0:54 ` Andy Furniss
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='000501c48500$4fcaee10$0802a8c0@monster' \
--to=mjoachimiak@poczta.onet.pl \
--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.