Am Montag, 25. Juni 2018, 13:17:17 CEST schrieb Bengt Gördén:
Den 2018-06-25 kl. 11:56, skrev Carlos E. R.:
Interrupts are tied to a certain core? I thought they were dynamically assigned to a non busy core.
Yes. Your right. I think I was a bit unclear. What I meant was that if you have the need to redirect one interrupt source to a certain core it can be done via smp-affinity. Normally you shouldn't need that but there are cases where it is of great importance. The two cases I referred to (router and DAW) is such cases. They are real time cases. Under heavy load in a recording (audio) situation you do not want disturbance in any way and as low latency as possible. In the case of router it's crucial if you have a production system and you don't have an out-of-band solution to access the router and the traffic is very high. We did this in three different projects about 11-13 years ago where we showed that 10Gbit/s forwarding in a Linux router is possible. There we redirected the ssh-port to CPU0 and the rest of the packets were handled by core CPU1-CPU7 so that the control plane were separated from data plane.
But to get back to the "watch cat /proc/interrupts". It's to see were the interrupts comes from.
Here is a shot of the interrupts: http://paste.opensuse.org/88070748 When the system is stuck, the interrupts on ahci and i915 count up, both on different cores. I guess thats the issue? Cheers Axel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org