From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Overbooking...
Date: Tue, 02 Sep 2003 21:02:21 +0000 [thread overview]
Message-ID: <marc-lartc-106253663309347@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106253615908798@msgid-missing>
On Tuesday 02 September 2003 22:56, Michal Jursa wrote:
> Hi,
> as I read in the Howto and messages in the conference the root class should
> be 'wide' enough to keep all the children classes, but I just wonder if
> there si some way to create guaranted rates with overbooking??
>
> For example:
> I've got 128kbit/s line and I'd like to have 4 users with guaranted rate
> 64kbit/s and ceil for example 96kbit/s, that means overbooking 1:2.
> So the question is: Is this possible and if yeah, then how..:)??
Euh, if you have 128kbit, how can you guarantee each one 64kbit/s???? That's
just not possible.
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:[~2003-09-02 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 20:56 [LARTC] Overbooking Michal Jursa
2003-09-02 21:02 ` 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-106253663309347@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox