From: Peter Surda <shurdeek@routehat.org>
To: lartc@vger.kernel.org
Subject: Re: Re: [LARTC] equal bandwidth for all IPs
Date: Sun, 22 May 2005 18:13:51 +0000 [thread overview]
Message-ID: <200542220135121972@mail.routehat.org> (raw)
In-Reply-To: <428CAD9F.8090403@phreaker.net>
On Sun, 22 May 2005 18:51:36 +0100 Andy Furniss <andy.furniss@dsl.pipex.com>
wrote:
>You could aswell as wrr consider esfq - you can only roughly divide what
>bandwidth you have, but the advantage over wrr is that you can choose a
>queue length for your link speed.
ESFQ is good, but isn't a panacea. You still can use esfq as a queueing
discipline for wrr's subclasses. In fact it's a perfect match, because you have
both fair division among sources AND among the connections made from the same
IP.
>I don't think you can di it with wrr and if you are shaping download
>from the internet it could be better.
You don't have to do this directly with WRR, but you can do it with HTB "above"
WRR. As for download, you can use IMQ.
Check out Route Hat's tc script. I was able to reach fair internet bandwidth
division for a peak of 700 users on a 8MBit line. Of course heavy P2P users
complained, but casual users were happy and so were the gamers, because they had
low latency with low but sustained transfer rate.
>Andy.
Yours sincerely,
shurdeek
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-05-22 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 15:15 [LARTC] equal bandwidth for all IPs ro0ot
2005-05-19 20:25 ` Krystian Antoni
2005-05-20 7:36 ` Andriy Korud
2005-05-20 10:00 ` Jesper Dangaard Brouer
2005-05-20 11:31 ` Peter Surda
2005-05-22 17:51 ` Andy Furniss
2005-05-22 18:13 ` Peter Surda [this message]
2005-05-22 21:12 ` 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=200542220135121972@mail.routehat.org \
--to=shurdeek@routehat.org \
--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.