summaryrefslogtreecommitdiffstats
path: root/init/Kconfig
diff options
context:
space:
mode:
authorVinicius Costa Gomes <vinicius.gomes@intel.com>2020-08-25 10:44:04 -0700
committerDavid S. Miller <davem@davemloft.net>2020-08-26 15:45:11 -0700
commit09e31cf0c528dac3358a081dc4e773d1b3de1bc9 (patch)
treefdc55133fa5af831114bf70c861cbac5bdeb53e7 /init/Kconfig
parent5fd99b5d9950d6300467ded18ff4e44af0b4ae55 (diff)
downloadlinux-09e31cf0c528dac3358a081dc4e773d1b3de1bc9.tar.gz
linux-09e31cf0c528dac3358a081dc4e773d1b3de1bc9.tar.bz2
linux-09e31cf0c528dac3358a081dc4e773d1b3de1bc9.zip
taprio: Fix using wrong queues in gate mask
Since commit 9c66d1564676 ("taprio: Add support for hardware offloading") there's a bit of inconsistency when offloading schedules to the hardware: In software mode, the gate masks are specified in terms of traffic classes, so if say "sched-entry S 03 20000", it means that the traffic classes 0 and 1 are open for 20us; when taprio is offloaded to hardware, the gate masks are specified in terms of hardware queues. The idea here is to fix hardware offloading, so schedules in hardware and software mode have the same behavior. What's needed to do is to map traffic classes to queues when applying the offload to the driver. Fixes: 9c66d1564676 ("taprio: Add support for hardware offloading") Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'init/Kconfig')
0 files changed, 0 insertions, 0 deletions