> When a driver supports both dcb and hardware offloaded mqprio, and > user is running mqprio and dcb tool concurrently, the configuration > set by each tool may be conflicted with each other because the dcb (for second 'each') s/each/the
> and mqprio may be using the same hardwere offload component and share s/hardwere/hardware > the tc system in the network stack. > > This patch adds a new offload type to indicate that the underlying > driver offload prio mapping as part of DCB. If the driver would be 'should' offload > incapable of that it would refuse the offload. User would then have > to explicitly request that qdisc offload.