[Cake] Multiple Hardware Queues

[dag dg]

(sorry for the spam Toke, still getting used to a new email client)

Thanks for the input, this is pretty much the info I was hoping for.
At this point I'll probably swap out the dual port NIC I have with
something more reasonable and put the i350 to work where its
performance will actually be used.

Really excited to have cake support in upstream.

Looking at usage I noticed there were a few cake configuration
parameters I may have missed when setting up my sqm-scripts config.
Right now I'm just using the "piece-of-cake.qos" example, with my
interface config file as:

# Uplink and Downlink values are in kbps
UPLINK=23000
DOWNLINK=330000

# SQM recipe to use. For more information, see /usr/lib/sqm/*.help
SCRIPT=piece_of_cake.qos

# Optional/advanced config

#ENABLED=1
#QDISC=cake

#LLAM=tc_stab
#LINKLAYER=none
#OVERHEAD=0
#STAB_MTU=2047
#STAB_TSIZE=512
#STAB_MPU=0

#ILIMIT=
#ELIMIT=
#ITARGET=
#ETARGET=

# ECN ingress resp. egress. Values are ECN or NOECN.
#IECN=ECN
#EECN=ECN

# Extra qdisc options ingress resp. egress
IQDISC_OPTS="nat docsis ingress"
EQDISC_OPTS="nat docsis ack-filter"

# CoDel target
#TARGET=5ms

#ZERO_DSCP_INGRESS=1
#IGNORE_DSCP_INGRESS=1

With the result being:

qdisc noqueue 0: dev lo root refcnt 2
qdisc fq_codel 0: dev enp6s0 root refcnt 2 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc cake 803b: dev enp2s0f0 root refcnt 9 bandwidth 23Mbit
besteffort triple-isolate nat ack-filter split-gso rtt 100.0ms noatm
overhead 18 mpu 64
qdisc ingress ffff: dev enp2s0f0 parent ffff:fff1 ----------------
qdisc mq 0: dev enp2s0f1 root
qdisc fq_codel 0: dev enp2s0f1 parent :8 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :7 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :6 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :5 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :4 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :3 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :2 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :1 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev tun0 root refcnt 2 limit 10240p flows 1024
quantum 1500 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc cake 803c: dev ifb4enp2s0f0 root refcnt 2 bandwidth 330Mbit
besteffort triple-isolate nat wash ingress split-gso rtt 100.0ms noatm
overhead 18 mpu 64

I don't fully understand the docsis option, is it supposed to show up
under the tc qdisc show or is it all in the background? I'm just
worried I'm not setting this up properly.