From: Thomas Gleixner <tglx@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Nicholas Mc Guire <der.herr@hofr.at>,
Clark Williams <williams@redhat.com>,
RT <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RT] oops in 4.1.3-rt3
Date: Wed, 19 Aug 2015 22:58:21 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1508192257300.3873@nanos> (raw)
In-Reply-To: <20150816115859.GD7004@linutronix.de>
On Sun, 16 Aug 2015, Sebastian Andrzej Siewior wrote:
> * Thomas Gleixner | 2015-08-04 14:05:10 [+0200]:
>
> >On Tue, 4 Aug 2015, Nicholas Mc Guire wrote:
> >> <snip>
> >> 3 root -2 0 0 0 0 R 60.3 0.0 5756:16 ksoftirqd/0
> >> 23 root -2 0 0 0 0 R 50.8 0.0 4948:08 ksoftirqd/2
> >> 17 root -2 0 0 0 0 S 50.6 0.0 4897:13 ksoftirqd/1
> >> 29 root -2 0 0 0 0 S 50.4 0.0 4953:24 ksoftirqd/3
> >
> >So ksoftirqd eats 50+% CPU on each core. On an idle system!?! Any
> >chance that you can get a function trace snapshot out of it?
>
> This might be a .config thing, device driver or user land behaviour.
> Usually ksoftirqd should remain (almost) idle because most of BH work
> remains in task-context and not in ksoftirqd. tasklets for instance
> should run in ksoftirqd. So a function trace or event tracing to figure
> out what is scheduling the softirq might give a pointer.
> I have here a AMD box with
>
> 3 root -2 0 0 0 0 S 1.3 0.0 126:16.31 ksoftirqd/0
> 18 root -2 0 0 0 0 S 1.3 0.0 136:55.85 ksoftirqd/1
> 30 root -2 0 0 0 0 S 1.3 0.0 138:50.52 ksoftirqd/3
> 24 root -2 0 0 0 0 S 1.0 0.0 143:54.28 ksoftirqd/2
>
> with a 15 days uptime. That one percent CPU usage on a idle system looks
> odd here, too.
Not really. If ksoftirqd takes 13us per invocation and you run with
HZ=1000 then this is reasonable.
Thanks,
tglx
next prev parent reply other threads:[~2015-08-19 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 19:27 [RT] oops in 4.1.3-rt3 Clark Williams
2015-08-04 8:08 ` Nicholas Mc Guire
2015-08-04 12:05 ` Thomas Gleixner
2015-08-16 11:58 ` Sebastian Andrzej Siewior
2015-08-19 20:58 ` Thomas Gleixner [this message]
2015-08-16 11:33 ` Sebastian Andrzej Siewior
2016-02-04 20:59 ` Clark Williams
2016-03-09 13:21 ` 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=alpine.DEB.2.11.1508192257300.3873@nanos \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=der.herr@hofr.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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