Hello Harald!

Unfortunately I don't think I can help you out here, but I'll try to add
some comments below. It would be really great if you are interested in
digging into this and giving some feedback (or maybe a patch to improve
the text in the manpage?).
We really need to expand the debian iproute package maintenance team
with someone who is able to dig into the documentation as the current
documentation definitely can be improved and there's alot more that
could be written. We have several concrete requests for areas that can
be improved by someone willing and able to dig into the details, please
see the wishlist area of http://bugs.debian.org/iproute .

I would suggest that you contact the people on the lartc.org mailing
lists. If noone there is able to help you could try to check if the
linux network developers on [EMAIL PROTECTED] has time to help out.


On fre, 2008-08-08 at 21:13 +0200, Harald Geyer wrote:
> Package: iproute
> Version: 20061002-3
> Severity: normal
> 
> In the man page tc-prio(8) there is the following table:
> TOS     Bits  Means                    Linux Priority    Band
> ------------------------------------------------------------
> 0x0     0     Normal Service           0 Best Effort     1
> 0x2     1     Minimize Monetary Cost   1 Filler          2
> 0x4     2     Maximize Reliability     0 Best Effort     1
> 0x6     3     mmc+mr                   0 Best Effort     1
> 0x8     4     Maximize Throughput      2 Bulk            2
> 0xa     5     mmc+mt                   2 Bulk            2
> 0xc     6     mr+mt                    2 Bulk            2
> 0xe     7     mmc+mr+mt                2 Bulk            2
> 0x10    8     Minimize Delay           6 Interactive     0
> 0x12    9     mmc+md                   6 Interactive     0
> 0x14    10    mr+md                    6 Interactive     0
> 0x16    11    mmc+mr+md                6 Interactive     0
> 0x18    12    mt+md                    4 Int. Bulk       1
> 0x1a    13    mmc+mt+md                4 Int. Bulk       1
> 0x1c    14    mr+mt+md                 4 Int. Bulk       1
> 0x1e    15    mmc+mr+mt+md             4 Int. Bulk       1
> 
> The description says:
> The  last column shows the result of the default priomap. On the
> command line, the default priomap looks like this:
> 1, 2, 2, 2, 1, 2, 0, 0 , 1, 1, 1, 1, 1, 1, 1, 1

I don't really understand the mapping between the table and the "command
line"-version either, but the last one seems to match my defaults:

$ sudo tc qdisc list
qdisc pfifo_fast 0: dev nvif root bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 
1 1
qdisc pfifo_fast 0: dev wan root bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 
1
qdisc pfifo_fast 0: dev fon root bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 
1
qdisc pfifo_fast 0: dev skif root bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 
1 1
qdisc ieee80211 8001: dev wmaster0 root 
qdisc pfifo_fast 0: dev ppp0 root bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 
1 1

My guess is that the table, which has a description which talks about
how to get the full output from tcpdump, is just an example. Another
reason to make me think this is the description of the second column,
which contains a pretty non-sense configuration (".. Maximum Throughput
AND Minimum Delay"...) that seems to be there just to prove a point how
the linux kernel remaps this (fourth column).
Maybe the first "default priomap" should really only be "priomap" to
make the description read:

"The  last column shows the result of the priomap. On the
command line, the default priomap looks like this:"


I can only guess though... don't know enough about this, and as
mentioned it would be really great if you where interested in digging
into this, talking to some people and see if you can come up with a
clarification that we can send to our upstream for inclusion.

> 
> To me it is not obvious how this maps together. Actually I suspect
> that the table is buggy, because for example band 0 is mentioned
> four times in the table but twice in the command line version ...
> 
> Do I miss something?
> 
> Kind regards,
> Harald
> 
> -- System Information:
> Debian Release: 4.0
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: i386 (i686)
> Shell:  /bin/sh linked to /bin/dash
> Kernel: Linux 2.6.18-6-686
> Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
> 
> Versions of packages iproute depends on:
> ii  libatm1                2.4.1-17          shared library for ATM 
> (Asynchrono
> ii  libc6                  2.3.6.ds1-13etch7 GNU C Library: Shared libraries
> ii  libdb4.3               4.3.29-8          Berkeley v4.3 Database Libraries 
> [
> 
> Versions of packages iproute recommends:
> ii  iproute-doc                   20061002-3 Professional tools to control 
> the 
> 
> -- no debconf information
> 
> 

Sorry for not being able to help out more, I hope this was of some help.
Feel free to ask for anything else that you thing I might be able to
help out with!

-- 
Regards,
Andreas Henriksson



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to