From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] wrr and htb help
Date: Sat, 08 Mar 2003 02:44:36 +0000 [thread overview]
Message-ID: <marc-lartc-104709170830867@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104703838205381@msgid-missing>
Hi again, Hare,
: i found wrr is good one, iam able to setup all and made them the
: available b/w equal to users for the available bandwidth and setup a
: web pages for the same to monitor
: now i have different Idea and need to setup, here iam not sure either
: its possible or not Please suggest
: i want to alocate bandwidth example
I presume you know how to build classes with children classes by
now...simply set your root class to your total available bandwidth, and
then create children classes according to your scheme (see the archives
for a discussion of shaping and FTP):
http://www.google.com/search?q=site%3Amailman.ds9a.nl+ftp+shaping
Since wrr (according to the docs available with the wrr distribution [1])
can and, it seems, should (?) function as a leaf queuing discipline, you
should be able to add a wrr qdisc to each of your leaf HTB classes. It
seems common to use a terminal SFQ qdisc in HTB classes. There's no
reason you couldn't choose WRR for your classes.
: 60% for http
: 20% ftp
: 10% all
: 5% ssh
: 5% voice
:
: and in 60% if the bandwidth for http, if the user are 6
: each user should get 60/6\x10% each user
: like other protocols tooo
: how can i achive this with wrr and htb
-Martin
[1] http://wipl-wrr.sourceforge.net/wrr.html
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-03-08 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 11:59 [LARTC] wrr and htb help hare ram
2003-03-08 2:44 ` Martin A. Brown [this message]
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=marc-lartc-104709170830867@msgid-missing \
--to=mabrown-lartc@securepipe.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 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.