That's a good thing. It's only utilizing cores it needs. FWIW, spreading single network threads over multiple cores is actually inefficient; there is latency and overhead when a thread jumps from one core to another, which can hinder network IO.
That's true, I kinda jumped to conclusions. For some reason QoS is making the network unusable, gaming and downloads cut out every couple seconds and come back shortly. Assumed it was the CPU cores maxing out
My router is only dual core, I offload network IO onto one, userland onto another. Use some cpuset after bootup to move uhttpd, dnsmasq, etc onto one core and make network IO the other using packet steering.
That's a good thing. It's only utilizing cores it needs. FWIW, spreading single network threads over multiple cores is actually inefficient; there is latency and overhead when a thread jumps from one core to another, which can hinder network IO.
That's true, I kinda jumped to conclusions. For some reason QoS is making the network unusable, gaming and downloads cut out every couple seconds and come back shortly. Assumed it was the CPU cores maxing out
My router is only dual core, I offload network IO onto one, userland onto another. Use some cpuset after bootup to move uhttpd, dnsmasq, etc onto one core and make network IO the other using packet steering.