For the initial version, it is enough to use the device hints from the SystemConfigurator to select the right Qdisc variant. Initially, cover just:
Offload
Software
In the future, we may add the tx-assisted variant. Another future improvement may be to initialize different configurator objects in the InterfaceManager constructor depending on the backed to use, so there is no selection in runtime.
On top of using the right taprio backend, the mapping also needs to be customized in the InterfaceManager initialization. The reason is, software taprio allows more flexibility than actual hardware, like modifying the traffic classes, and the meaning of the mapping is also different. In order to implement the change:
Rename Mapping as MappingFixed
Rename MappingNaive as MappingFlexible
If the hint uses hardware Qbv, select the MappingFixed, otherwise the MappingFlexible
On top of providing the hints (https://github.com/Avnu/detd/issues/21), this issue adds the actual configuration for the interface.
For the initial version, it is enough to use the device hints from the SystemConfigurator to select the right Qdisc variant. Initially, cover just:
In the future, we may add the tx-assisted variant. Another future improvement may be to initialize different configurator objects in the InterfaceManager constructor depending on the backed to use, so there is no selection in runtime.
On top of using the right taprio backend, the mapping also needs to be customized in the InterfaceManager initialization. The reason is, software taprio allows more flexibility than actual hardware, like modifying the traffic classes, and the meaning of the mapping is also different. In order to implement the change: