From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jens Koehler <jenskxxx@googlemail.com>, linux-rt-users@vger.kernel.org
Subject: Re: hrtimer: interrupt took 10252 ns - meaning?
Date: Fri, 1 Jul 2016 12:49:26 +0200 [thread overview]
Message-ID: <9f943b0e-12f5-2779-0bba-c4bc2b7357fa@linutronix.de> (raw)
In-Reply-To: <CAL7_A_VUiLH9JBkL8HBrUaAn6_yF+3jefXHMwGFS8Sr4g29q0A@mail.gmail.com>
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
next prev parent reply other threads:[~2016-07-01 11:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 9:16 hrtimer: interrupt took 10252 ns - meaning? Jens Koehler
2016-07-01 10:49 ` Sebastian Andrzej Siewior [this message]
2016-08-08 16:45 ` Sebastian Andrzej Siewior
2016-08-12 9:47 ` Jens Koehler
2016-08-12 12:37 ` Sebastian Andrzej Siewior
2016-08-12 18:48 ` Jens Koehler
2016-09-08 10:36 ` Jens Koehler
2016-09-08 11:37 ` Sebastian Andrzej Siewior
2016-09-12 9:16 ` Stanislav Meduna
2016-09-12 10:07 ` Sebastian Andrzej Siewior
2016-09-12 10:13 ` Stanislav Meduna
2016-09-12 10:21 ` Vasudev Kamath
-- strict thread matches above, loose matches on Subject: below --
2016-06-01 7:46 Jens Koehler
2016-06-03 15:59 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9f943b0e-12f5-2779-0bba-c4bc2b7357fa@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jenskxxx@googlemail.com \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).