From: "Christian Worm Mortensen" <worm@dkik.dk>
To: <lartc@mailman.ds9a.nl>, <linux-kernel@vger.kernel.org>,
<linux-net@vger.kernel.org>
Subject: [ANNOUNCE] New version of the WRR network scheduler
Date: Fri, 2 Mar 2001 23:05:37 +0100 [thread overview]
Message-ID: <003a01c0a364$e95cbd00$5f01a8c0@worm> (raw)
Hi,
I have just released a new version of the WRR scheduler supporting the
2.4 kernels besides 2.2 as always . The WRR scheduler is an extension
to the Traffic Control/network bandwidth management part of the Linux
kernels. The scheduler was developed to support distributing bandwidth
on a shared Internet connection fairly between local machines.
Further comments:
* As a default all local machines will get equally much
of the bandwidth if they have sufficient demand. This
is obtained by doing so-called weighted round robin (wrr)
scheduling.
* It is possible to give machines transferring much data
over a long or short period of time less bandwidth.
* It can work on a bridge, a router or on a firewall.
* Supports accounting locally generated masqgraded packets
to the correct local machine.
* On the WRR home page an extension is available which
includes patches for Squid and the Nec socks5 proxy servers
so that proxied packets can also be accounted to the
correct local machine.
* Includes a configuration file based set of scripts that
will setup everything without changing your basic network
setup. The scripts will allow you to shape both incoming
and outgoing traffic.
Christian
next reply other threads:[~2001-03-02 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 22:05 Christian Worm Mortensen [this message]
2001-03-02 22:27 ` [ANNOUNCE] New version of the WRR network scheduler Aaron Tiensivu
-- strict thread matches above, loose matches on Subject: below --
2001-03-02 22:33 Christian Worm Mortensen
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='003a01c0a364$e95cbd00$5f01a8c0@worm' \
--to=worm@dkik.dk \
--cc=lartc@mailman.ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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