I made some testing with streaming and see while routing between lan and wan/pppoe interrupts counting up only on cpu0. It stops from time to time.i have not much cpu usage in top,but it seems that interrupts causing this
Afair there was a way ro change cpu or maybe use all cpus…but don’t remember how. Afaik it was called affinity,but found only the crypto driver thread…
so only first cpu is used…some more interrupts operating only on cpu0. i found no dropping or similar on networking interfaces i use for this (eth0, lan0 and wan), vlan and pppoe had no statictics in ethtool
i tried moving irq to different CPU (counting not clear)
after ~1 minute i see these (~1000 interupts /min)…isn’t this much??
i guess the interrupts are caused by NAT…my structure is wan + vlan + pppoe with NAT => routed to lan0 through iptables (which may also cause CPU-load/interrupts)
How does it manifest? I haven’t been using R2 much lately, but starting yesterday, I’ve been using it to transfer files and I haven’t experienced any timeouts. It is a gateway between NAS and PC and it has been stable so far.
So you need to restart after timeout occurs? Timeout does not sound to me like a critical error that needs restart, but I remember that I had to restart R2, because it stopped responding.
it turns out that issue was caused by to big packets (MTU1500 vs. pppoe 1492) and my SmartTV ignored the MTU broadcast from dnsmasq (which was working on laptop)
i added a MSS-Fix to my nftables
chain FORWARD {
type filter hook forward priority 0; policy drop;
#https://wiki.nftables.org/wiki-nftables/index.php/Mangling_packet_headers
#MSS fix for pppoe 1500 - 8 (pppoe) - 20 (ipv4) - 20 (TCP)
oifname $ifwan tcp flags syn tcp option maxseg size set 1452
#oifname $ifwan tcp flags syn tcp option maxseg size set rt mtu
and now it is working so far.
while changing smp_affinity i noticed that irq-numbers have changed from 5.4 to 5.10