From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Another sharing tehnique, is this possible ?
Date: Sun, 18 Aug 2002 20:03:40 +0000 [thread overview]
Message-ID: <marc-lartc-102970110617500@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102959019628424@msgid-missing>
On Sunday 18 August 2002 21:56, Ivo De Decker wrote:
> On Sun, Aug 18, 2002 at 09:48:09PM +0200, Stef Coene wrote:
> > Normally, each class gets the rate as a minimum. After that, the
> > remaning bandwidth is divided according to the proportions of the rate
> > (more accurate, the quantums) but the classes with the lowest prio will
> > be serverd first. So only remaining bandwidth will be influenced with
> > the prio parameter.
> >
> > And giving a class rate 0 is a strange idea :)
>
> Well, not really:
>
> There might be some sorts of traffic (eg backups) that aren't really
> prioritary. The classes of this traffic could use borrowed bandwith
> exclusively: if there is no other traffic (or not enough to fill the total
> available bandwith), the backups can happen, but if there is other (higher
> priority) traffic, the backups can wait till that traffic lessens (assuming
> this eventually happens, off course).
>
>
> The question is: is this possible?
If you have a total of 100, give backup 1 and the rest 99. As long as there
is no other traffic, backup can get the full bandwidth. But if there is
other traffic, it can use up to 99.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-08-18 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 13:14 [LARTC] Another sharing tehnique, is this possible ? raptor
2002-08-18 19:48 ` Stef Coene
2002-08-18 20:03 ` Stef Coene [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-102970110617500@msgid-missing \
--to=stef.coene@docum.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.