Switch weights on the second XGS 3300: the shares follow the table once port 0's pause is off, 2026-11-19
os-trafficpriority gives a class a minimum - a part of a full port that its switch queue keeps - by
the switch's weight table: os-xgs-npu's switch tool (src/opnsense/scripts/xgs/switch_qos.py) writes
one sequence of queue numbers for the whole 88E6193X chip, and a port in weighted mode serves its
queues in that order. Written for two classes at 30 and 20 turns, the table did not show: earlier the
same day the class at 30 took 914.5 to 924.2 Mbit/s at line rate and the class at 20 took 10.3 to
18.4. These runs found why, and the lever: with port 0's pause off - the switch's flow control
toward the coprocessor - the shares follow the table, 59:41 for 30:20 and 38:62 for 30:50, for 1 to
3 % of the line rate with two streams.
The whole page, with how it was taken and what it does not show: Switch weights on the second XGS 3300: the shares follow the table once port 0's pause is off, 2026-11-19.
The discussion of this page is held in the project's GitHub Discussions. Showing it here loads giscus from giscus.app and GitHub, and writing in it needs a GitHub account - what that means.