Displaying 2 results from an estimated 2 matches for "linux_prior".
2007 Aug 29
1
Alternative section to the HOWTO...
...4 (Int. Bulk)
This mapping is hard-coded and can not be adjusted, only the default priomap
can be changed, to clarify, the whole process for an IPv4 packet would be:
ToS value ------mapping------> Linux Priority ------priomap ------> Band
A few extra comments:
- The ToS-to-Linux_Priority mapping is made at the very beggining of
the routing process, even before the packet enters in the iptables chains.
This means that changing the ToS field of the packet with iptable''s "-j
TOS --set-tos" flags, will not change neither its linux priority nor
the band...
2007 Aug 28
2
prio bands and ignored priomap when any tc filter is present
Today I''ve noticed a bit strange (?) behaviour when prio qdisc is used.
Example (having no filters/qdisc/etc. at the start) :
Add simple 9 bands qdisc, set each mapping to lowest priority band:
tc qdisc add dev $eth root handle 1: prio bands 9 priomap 8 8 8 8 8 8 8 8 8
8 8 8 8 8 8 8
If I do just that, all is fine - whole traffic ends in 9th band, what can
easily be verified by tc -s