Re: hrtimer: interrupt took 10252 ns - meaning?
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: 2016-07-01 11:09:59
On 06/13/2016 11:16 AM, Jens Koehler wrote:
I found now out that the problem with RT throttling could happen when my application sends UDP broadcasts (and receive its own broadcast). Is this an already known problem?
Not to my knowledge. Could you please send a (small) testcase and your kernel config? I then would take look a check how serious it is :)
[137482.258011] hrtimer: interrupt took 9434 ns [178458.961966] NOHZ: local_softirq_pending 102 [178458.967583] NOHZ: local_softirq_pending 102 [178458.973295] NOHZ: local_softirq_pending 102 [178458.980249] NOHZ: local_softirq_pending 102 [178458.984994] NOHZ: local_softirq_pending 102 [178458.990582] NOHZ: local_softirq_pending 102 [178458.996292] NOHZ: local_softirq_pending 102 [178459.000348] [sched_delayed] sched: RT throttling activated Jens
Sebastian