Tc qdisc shows fq_codel?

i suspect i just don't understand the output, but if my /etc/config/sqm is:

config queue 'eth0'
        option interface 'eth0.2'
        option qdisc_advanced '0'
        option debug_logging '0'
        option verbosity '5'
        option qdisc 'cake'
        option script 'piece_of_cake.qos'
        option linklayer 'ethernet'
        option upload '0'
        option enabled '1'
        option download '70500'
        option overhead '26'

why does tc -d qdisc show fq_codel:

# tc -d qdisc
qdisc noqueue 0: dev lo root refcnt 2 
qdisc mq 0: dev eth0 root 
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc mq 0: dev eth1 root 
qdisc fq_codel 0: dev eth1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc noqueue 0: dev br-lan root refcnt 2 
qdisc noqueue 0: dev eth1.1 root refcnt 2 
qdisc noqueue 0: dev eth0.2 root refcnt 2 
qdisc ingress ffff: dev eth0.2 parent ffff:fff1 ---------------- 
qdisc noqueue 0: dev wg_admin root refcnt 2 
qdisc noqueue 0: dev wlan1 root refcnt 2 
qdisc noqueue 0: dev wlan0 root refcnt 2 
qdisc fq_codel 0: dev tun0 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc noqueue 0: dev wg0 root refcnt 2 
qdisc fq_codel 0: dev pppoe-wan root refcnt 2 limit 10240p flows 1024 quantum 1518 target 5.0ms interval 100.0ms memory_limit 4Mb ecn 
qdisc cake 800c: dev ifb4eth0.2 root refcnt 2 bandwidth 70500Kbit besteffort triple-isolate nonat wash no-ack-filter split-gso rtt 100.0ms noatm overhead 26 

I believe because OpenWrt defaults to fq_codel for all interfaces. IIMHO fq_codel is a great all purpose qdisc and certainly better than the old linux default pfifo_fast....

But note that you also have:

So the expected single cake download instance shows up as well (upload 0 disables sqm for the upload direction, why do you prefer to do that?).

oh so it all looks fine? i am a little unclear as to what the overhead should be configured as, i had it as 34 but then i read (i think it was your comment actually :slight_smile: ) that if i had the sqm instance on the ethernet interface rather than on pppoe_wan i should subtract 8 so i changed it to 26.

re the upload 0, because it didn't seem to be necessary in dslreports speedtest, i never got any bufferbloat on the upload test. is there something else i should be checking?

the egress(upload) side is where the sqm takes effect, the ingress side does not shape unless you are using special scripts. For pppoe I use 27 as per openwrt recommendations.