From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] prio
Date: Sun, 02 Jan 2005 00:07:28 +0000 [thread overview]
Message-ID: <41D73B40.2000207@dsl.pipex.com> (raw)
kasp wrote:
> Hi!
>
> Could somebody tell me, what is difference between these two prio
> parameters in http://lartc.org/lartc.html#AEN2241
>
> 1) tc class add dev $DEV parent 1:1 classid 1:10 htb rate ${UPLINK}kbit burst 6k prio 1
> ^^^^^^
> AND
>
> 2) tc filter add dev $DEV parent 1:0 protocol ip prio 10 u32 match ip tos 0x10 0xff flowid 1:10
> ^^^^^^^
>
> Why they aren't equal?
> Is there some rules to set prio for each of them?
>
>
prio on htb mainly affects the way it shares excess bandwidth - the
lower the number the higher the priority.
On filters it lets you choose the order your rules get tested against
the packets.
I haven't look at the script - but the prio on the filter is unlikely to
make any noticable difference if changed/ommitted.
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2005-01-02 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 0:07 Andy Furniss [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-25 17:08 [LARTC] prio kasp
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=41D73B40.2000207@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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