From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] isolated/sharing/bounded/borrow - help please
Date: Fri, 24 Jan 2003 18:09:13 +0000 [thread overview]
Message-ID: <marc-lartc-104343184323247@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104342144805615@msgid-missing>
On Friday 24 January 2003 16:16, ray-nger wrote:
> Hello!
> Could you tell me some answers about subj?
> Isolated class will not lend out bandwidth.
> sharing - will always lend out?
> not isol. non sharing - ?????
>
> The same for bounded/borrow:
> bounded - will not borrow.
> not bound not borrow - ???
Forget the isolated parameter. It's not working and can distrurb your cbq
setup.
> Or example:
> We have 2 class. Class 1st take Xkbit, and must always get his speed,
> if it needed.
> Class 2nd must have rest of bandwidht, include unused kbits from
> class 1st.
> I confuse to solve this....help, please!
Use htb.
See www.docum.org for more info about shaping/htb.
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-01-24 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 15:16 [LARTC] isolated/sharing/bounded/borrow - help please ray-nger
2003-01-24 18:09 ` 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-104343184323247@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.