Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1208236 > unrolled thread
| Started by | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| First post | 2015-08-16 14:00 +0200 |
| Last post | 2015-08-19 23:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RT] oops in 4.1.3-rt3 Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2015-08-16 14:00 +0200
Re: [RT] oops in 4.1.3-rt3 Thomas Gleixner <tglx@linutronix.de> - 2015-08-19 23:00 +0200
| From | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| Date | 2015-08-16 14:00 +0200 |
| Subject | Re: [RT] oops in 4.1.3-rt3 |
| Message-ID | <pY4Lw-7DG-5@gated-at.bofh.it> |
* 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. >Thanks, > > tglx Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Date | 2015-08-19 23:00 +0200 |
| Message-ID | <pZiCL-hP-21@gated-at.bofh.it> |
| In reply to | #1208236 |
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web