[LARTC] tc: weight, defmap and split usage?

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Some (non urgent) questions about "tc" parameters:

What is "weight" for? We've seen that leaving it out of our script causes
error/warnings like:

CQB: class 00010012 had bad quantum==0, repaired.

Which values should it have and why?

When should one use the "split" and "defmap" parameters? I guess they can
be used to specify the best effort class, but what value should split have
and how do you read/understand the hex value of defmap?


A last note to the HOWTO maintainers: thanks.






[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux