From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] PRIO on non-leaf classes?
Date: Wed, 25 Jan 2006 15:00:21 +0000 [thread overview]
Message-ID: <20060125150021.GB10755@EIS> (raw)
In-Reply-To: <43D77CEE.8000001@obs.bg>
On Wed, Jan 25, 2006 at 03:28:14PM +0200, openswan wrote:
> I'm using HTB and would like to ask is it correct to put "PRIO" on
> non-leaf classes ? I know that on leaf classes it's correct and
> determines how the excess bandwidth is distributed among non-leaf classes.
Depends on what you mean by "PRIO". If you're talking about the
class parameter prio (in lower-case letters), then it's correct,
the PRIO QDisc however, can not be attached to anything but the
device itself (root qdisc) or a leaf class.
Regards
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-01-25 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 13:28 [LARTC] PRIO on non-leaf classes? openswan
2006-01-25 14:07 ` Dmytro O. Redchuk
2006-01-25 15:00 ` Andreas Klauer [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=20060125150021.GB10755@EIS \
--to=andreas.klauer@metamorpher.de \
--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.