From: "Soulfly" <zob_soulfly@hotmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] typo ?
Date: Thu, 04 Apr 2002 16:28:00 +0000 [thread overview]
Message-ID: <marc-lartc-101793764806755@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101790652812797@msgid-missing>
"Mihai RUSU" wrote
> Hi
>
> While reading the HOWTO (pdf downloaded and printed last night) I have
> noticed a little strange thing. In the 9.2.1 chapter, explaining the
> pfifo_fast qdisc, it is shown a TOS field mapping table and also it
> appears a command line version:
>
> "The last column shows the result of the default priomap. On the
> commandline, the default priomap looks like this:
> 1, 2, 2, 2, 1, 2, 0, 0 , 1, 1, 1, 1, 1, 1, 1, 1
>
> This means that priority 4, for example, gets mapped to band number 1. The
> priomap also allows you to list higher priorities (> 7) which do not
> correspond to TOS mappings, but which are set by other means."
>
> The numbers on the command line version are 16, thus I presume its a one
> to one corespondation to the table, only that it is completly different. I
> dont see any explanation why it is like that. Shouldnt that be:
> 1,2,1,1,2,2,2,2,0,0,0,0,1,1,1,1 ?
>
> Thanks
>
> ----------------------------
> Mihai RUSU
>
nope. Try the following:
# tc qdisc del dev eth0 root
# tc qdisc add dev eth0 root handle 1: prio
# tc -s qdisc ls dev eth0
qdisc prio 1: bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 455336 bytes 1237 pkts (dropped 0, overlimits 0)
which is the default priomap on the commandline. The one you mention is the
priomap in the kernel for pfifo_fast.
I usually set the priomap manually to get the latter priomap. example:
tc qdisc add dev eth0 root handle 1: prio bands 4 priomap 2 3 2 2 3 3 3 3 1
1 1 1 2 2 2 2
(which is the kernels default + 1, here I use the 0 band for very important
traffic which goes above the TOS-field.)
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-04-04 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 7:45 [LARTC] typo ? Mihai RUSU
2002-04-04 16:28 ` Soulfly [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-101793764806755@msgid-missing \
--to=zob_soulfly@hotmail.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 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.