From: Radoslav Kolev <radolin@del.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Guaranteed bandwidth per connection
Date: Wed, 21 Apr 2004 13:54:11 +0000 [thread overview]
Message-ID: <40867D03.8080904@del.bg> (raw)
In-Reply-To: <20040421112559.7ff111ab.j.vriesman@prompt.nl>
Hi!Jeroen Vriesman wrote:
>In stead of defining a min/max for a certain type of traffic (e.g. http, ftp whatever), I would like to define a "minimum guaranteed bandwidth per connection".
>e.g. An application connecting to port X would get 10kbit/s guaranteed, the next connection to port X would also get 10kbit/s etc.
>
>Would be something like having N (the maximum number of connections) HTB classes, and put every new connection in another class.
>
>
I don't know how you can put every new connection in a new class, but
why don't you try this:
Decide what will be the maximum number of connections you want to
provide the guaranteed minimum and how much will it be (kbit/s).
If for example we take connections to port 80, create a HTB class with
rate=max_conn*guaranteed_rate and classify all traffic to port 80 to it.
Then add an SFQ behind. This way if there is a fewer number of
connections than you planned for each will get
(class_rate/connections)kbit, which
will more than the guaranteed minimun. If the number is equal to the
number of connections, the SFQ will make sure that no particular connection
take over the bandwitdh, and evey connection will get it's guaranteed
minimum. If there are more connections than you expected, each will get
an equal portion of the available bandwidth. Actually that's exactly
what SFQ is designed for, to distribute the available bandwidth equally
to every connection.
Greets,
Rado
_______________________________________________
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-04-21 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 9:25 [LARTC] Guaranteed bandwidth per connection Jeroen Vriesman
2004-04-21 13:54 ` Radoslav Kolev [this message]
2004-04-21 14:42 ` Jeroen Vriesman
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=40867D03.8080904@del.bg \
--to=radolin@del.bg \
--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.