Hi, on a 6.1.90-rt30 system we occasionally see NET_RX softirq work being done in the ktimers thread. This could be related to running ksoftirqd at a RT priority, but this by itself should not be problematic as PI boosting can result in the same priority. Is this already a known issue? Does it only result in delayed timer handling, or is it also problematic from a functional PoV? I quickly checked the linux-next tree, but did not find any fixing commit. Extract from an irq trace: ktimers/1-29 [001] ...s.12 ... softirq_entry: vec=3 [action=NET_RX] ktimers/4-53 [004] ...s.12 ... softirq_entry: vec=3 [action=NET_RX] ktimers/4-53 [004] ...s.12 ... softirq_entry: vec=3 [action=NET_RX] Best regards, Felix -- Siemens AG Linux Expert Center Friedrich-Ludwig-Bauer-Str. 3 85748 Garching, Germany
