Awhile ago I submitted this iproute2 patch:
https://patchwork.ozlabs.org/patch/784165/

And the corresponding kernel patch:
https://patchwork.ozlabs.org/patch/783696/

To allow the setting of arbitrary qdisc size table so that the packet
scheduler code in __qdisc_calculate_pkt_len charges the correct
bandwidth per my custom link layer.  These patches were not applied
because the reviewers didn't like that I added another enumeration to
the kernel's UAPI:  TC_LINKLAYER_CUSTOM.

My question is: why is the setting of the STAB not exposed to
userspace applications?  This seems to be a powerful feature that is
more generic than hard-coding the STABs for TC_LINKLAYER_ETHERNET and
TC_LINK_LAYER_ATM.  Or maybe I'm missing something and there is
mechanism to do this without my iproute2 patch?

Reply via email to