Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1297683 > unrolled thread
| Started by | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| First post | 2015-12-24 00:00 +0100 |
| Last post | 2016-01-14 13:00 +0100 |
| Articles | 19 — 6 participants |
Back to article view | Back to linux.kernel
[ANNOUNCE] 4.4-rc6-rt1 Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2015-12-24 00:00 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-01-01 08:20 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Thomas Gleixner <tglx@linutronix.de> - 2016-01-01 10:20 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-01-01 10:50 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-01-13 19:00 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Grygorii Strashko <grygorii.strashko@ti.com> - 2016-01-13 19:40 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-01-14 16:00 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-01-14 10:40 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-01-14 15:20 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-01-14 15:40 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Thomas Gleixner <tglx@linutronix.de> - 2016-01-14 15:40 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-01-14 16:00 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Thomas Gleixner <tglx@linutronix.de> - 2016-01-14 16:10 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-01-14 17:10 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Tim Sander <tim@krieglstein.org> - 2016-01-07 13:20 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-01-13 14:50 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 (arm64) "Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com> - 2016-01-13 12:50 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 (arm64) Sebastian Andrzej Siewior <bigeasy@linutronix.de> - 2016-01-13 14:50 +0100
Re: [ANNOUNCE] 4.4-rc6-rt1 (arm64) "Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com> - 2016-01-14 13:00 +0100
| From | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| Date | 2015-12-24 00:00 +0100 |
| Subject | [ANNOUNCE] 4.4-rc6-rt1 |
| Message-ID | <qJ0xY-74S-5@gated-at.bofh.it> |
Please don't continue reading before christmas eve (or morning,
depending on your schedule). If you don't celebrate christmas,
well go ahead.
Dear RT folks!
I'm pleased to announce the v4.4-rc6-rt1 patch set. I tested it on my
AMD A10, 64bit. Nothing exploded so far, filesystem is still there.
I haven't tested it on anything else. Before someone asks: this does not
mean it does *not* work on ARM I simply did not try it.
If you are brave then download it, install it and have fun. If something
breaks, please report it. If your machine starts blinking like a
christmas tree while using the patch then *please* send a photo.
Changes since v4.1.15-rt17:
- rebase to v4.4-rc6
Known issues (inherited from v4.1-RT):
- bcache stays disabled
- CPU hotplug is not better than before
- The netlink_release() OOPS, reported by Clark, is still on the
list, but unsolved due to lack of information
- Christoph Mathys reported a stall in cgroup locking code while using
Linux containers.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git v4.4-rc6-rt1
The RT patch against 4.4-rc6 can be found here:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.4/patch-4.4-rc6-rt1.patch.xz
The split quilt queue is available at:
https://cdn.kernel.org/pub/linux/kernel/projects/rt/4.4/patches-4.4-rc6-rt1.tar.xz
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 | Mike Galbraith <umgwanakikbuti@gmail.com> |
|---|---|
| Date | 2016-01-01 08:20 +0100 |
| Message-ID | <qM2ae-76b-7@gated-at.bofh.it> |
| In reply to | #1297683 |
On Thu, 2015-12-31 at 10:24 -0600, Clark Williams wrote:
> I pulled this update and tried it on my laptop (i7 quad-core with HT)
> and an Atom testbox. I'm seeing a change in the cpu utilization of
> ksoftirqd between 4.1.15-rt17 and 4.4-rc2-rt1, where the per-cpu
> ksoftirqd threads are running at between 25-40% utilization:
>
> top - 10:15:57 up 13:46, 2 users, load average: 9.44, 9.30, 8.93
> Tasks: 188 total, 2 running, 186 sleeping, 0 stopped, 0 zombie
> %Cpu(s): 4.7 us, 53.6 sy, 0.0 ni, 37.4 id, 0.1 wa, 0.0 hi, 4.2 si, 0.0 st
> KiB Mem : 4046064 total, 480548 free, 179528 used, 3385988 buff/cache
> KiB Swap: 5177340 total, 5169908 free, 7432 used. 3785624 avail Mem
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 3 root -2 0 0 0 0 S 37.3 0.0 307:52.44 ksoftirqd/0
> 32 root -2 0 0 0 0 S 37.3 0.0 308:08.72 ksoftirqd/2
> 42 root -2 0 0 0 0 R 37.3 0.0 308:32.84 ksoftirqd/3
> 22 root -2 0 0 0 0 S 26.9 0.0 222:29.82 ksoftirqd/1
> 1 root 20 0 46628 6980 4976 S 1.3 0.2 0:13.98 systemd
> 22358 williams 20 0 159980 4552 3780 R 1.0 0.1 0:00.39 top
Heh, I didn't notice immediately because I throttle nohz, am seeing
only tiny utilization (but nohz idle isn't working). With throttle
patch removed, box is screaming, expires=4294990471 pokes eyeball.
swapper 0 [003] 392.708321: timer:hrtimer_cancel: hrtimer=0xffff88041ecce720
swapper 0 [003] 392.708321: timer:hrtimer_start: hrtimer=0xffff88041ecce720 function=tick_sched_timer/0x0 expires=4294990471 softexpires=4294990471
swapper 0 [003] 392.708323: timer:hrtimer_cancel: hrtimer=0xffff88041ecce720
swapper 0 [003] 392.708324: timer:hrtimer_expire_entry: hrtimer=0xffff88041ecce720 now=392697118535 function=tick_sched_timer/0x0
swapper 0 [003] 392.708325: timer:hrtimer_expire_exit: hrtimer=0xffff88041ecce720
swapper 0 [003] 392.708326: timer:hrtimer_start: hrtimer=0xffff88041ecce720 function=tick_sched_timer/0x0 expires=392700750000 softexpires=392700750000
swapper 0 [003] 392.708328: timer:tick_stop: success=yes msg=
swapper 0 [003] 392.708329: timer:hrtimer_cancel: hrtimer=0xffff88041ecce720
swapper 0 [003] 392.708329: timer:hrtimer_start: hrtimer=0xffff88041ecce720 function=tick_sched_timer/0x0 expires=4294990471 softexpires=4294990471
swapper 0 [003] 392.708331: timer:hrtimer_cancel: hrtimer=0xffff88041ecce720
swapper 0 [003] 392.708332: timer:hrtimer_expire_entry: hrtimer=0xffff88041ecce720 now=392697126313 function=tick_sched_timer/0x0
swapper 0 [003] 392.708333: timer:hrtimer_expire_exit: hrtimer=0xffff88041ecce720
swapper 0 [003] 392.708334: timer:hrtimer_start: hrtimer=0xffff88041ecce720 function=tick_sched_timer/0x0 expires=392700750000 softexpires=392700750000
swapper 0 [003] 392.708336: timer:tick_stop: success=yes msg=
--
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] | [next] | [standalone]
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Date | 2016-01-01 10:20 +0100 |
| Message-ID | <qM42m-9N-7@gated-at.bofh.it> |
| In reply to | #1299848 |
On Fri, 1 Jan 2016, Mike Galbraith wrote: > On Thu, 2015-12-31 at 10:24 -0600, Clark Williams wrote: > > I pulled this update and tried it on my laptop (i7 quad-core with HT) > > and an Atom testbox. I'm seeing a change in the cpu utilization of > > ksoftirqd between 4.1.15-rt17 and 4.4-rc2-rt1, where the per-cpu > > ksoftirqd threads are running at between 25-40% utilization: > > > > top - 10:15:57 up 13:46, 2 users, load average: 9.44, 9.30, 8.93 > > Tasks: 188 total, 2 running, 186 sleeping, 0 stopped, 0 zombie > > %Cpu(s): 4.7 us, 53.6 sy, 0.0 ni, 37.4 id, 0.1 wa, 0.0 hi, 4.2 si, 0.0 st > > KiB Mem : 4046064 total, 480548 free, 179528 used, 3385988 buff/cache > > KiB Swap: 5177340 total, 5169908 free, 7432 used. 3785624 avail Mem > > > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > 3 root -2 0 0 0 0 S 37.3 0.0 307:52.44 ksoftirqd/0 > > 32 root -2 0 0 0 0 S 37.3 0.0 308:08.72 ksoftirqd/2 > > 42 root -2 0 0 0 0 R 37.3 0.0 308:32.84 ksoftirqd/3 > > 22 root -2 0 0 0 0 S 26.9 0.0 222:29.82 ksoftirqd/1 > > 1 root 20 0 46628 6980 4976 S 1.3 0.2 0:13.98 systemd > > 22358 williams 20 0 159980 4552 3780 R 1.0 0.1 0:00.39 top > > Heh, I didn't notice immediately because I throttle nohz, am seeing > only tiny utilization (but nohz idle isn't working). With throttle > patch removed, box is screaming, expires=4294990471 pokes eyeball. > > swapper 0 [003] 392.708321: timer:hrtimer_cancel: hrtimer=0xffff88041ecce720 > swapper 0 [003] 392.708321: timer:hrtimer_start: hrtimer=0xffff88041ecce720 function=tick_sched_timer/0x0 expires=4294990471 softexpires=4294990471 There is a major hickup in the hrtimer RT conversion. I'll have a look next week. 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] | [next] | [standalone]
| From | Mike Galbraith <umgwanakikbuti@gmail.com> |
|---|---|
| Date | 2016-01-01 10:50 +0100 |
| Message-ID | <qM4vn-w4-1@gated-at.bofh.it> |
| In reply to | #1299863 |
On Fri, 2016-01-01 at 10:14 +0100, Thomas Gleixner wrote: > On Fri, 1 Jan 2016, Mike Galbraith wrote: > > On Thu, 2015-12-31 at 10:24 -0600, Clark Williams wrote: > > > I pulled this update and tried it on my laptop (i7 quad-core with HT) > > > and an Atom testbox. I'm seeing a change in the cpu utilization of > > > ksoftirqd between 4.1.15-rt17 and 4.4-rc2-rt1, where the per-cpu > > > ksoftirqd threads are running at between 25-40% utilization: > > > > > > top - 10:15:57 up 13:46, 2 users, load average: 9.44, 9.30, 8.93 > > > Tasks: 188 total, 2 running, 186 sleeping, 0 stopped, 0 zombie > > > %Cpu(s): 4.7 us, 53.6 sy, 0.0 ni, 37.4 id, 0.1 wa, 0.0 hi, 4.2 si, 0.0 st > > > KiB Mem : 4046064 total, 480548 free, 179528 used, 3385988 buff/cache > > > KiB Swap: 5177340 total, 5169908 free, 7432 used. 3785624 avail Mem > > > > > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > > 3 root -2 0 0 0 0 S 37.3 0.0 307:52.44 ksoftirqd/0 > > > 32 root -2 0 0 0 0 S 37.3 0.0 308:08.72 ksoftirqd/2 > > > 42 root -2 0 0 0 0 R 37.3 0.0 308:32.84 ksoftirqd/3 > > > 22 root -2 0 0 0 0 S 26.9 0.0 222:29.82 ksoftirqd/1 > > > 1 root 20 0 46628 6980 4976 S 1.3 0.2 0:13.98 systemd > > > 22358 williams 20 0 159980 4552 3780 R 1.0 0.1 0:00.39 top > > > > Heh, I didn't notice immediately because I throttle nohz, am seeing > > only tiny utilization (but nohz idle isn't working). With throttle > > patch removed, box is screaming, expires=4294990471 pokes eyeball. > > > > swapper 0 [003] 392.708321: timer:hrtimer_cancel: hrtimer=0xffff88041ecce720 > > swapper 0 [003] 392.708321: timer:hrtimer_start: hrtimer=0xffff88041ecce720 function=tick_sched_timer/0x0 expires=4294990471 softexpires=4294990471 > > There is a major hickup in the hrtimer RT conversion. I'll have a look next > week. Yeah, fixing up the screaming didn't do wonderful things, box is a lethargic slug. I'll have a poke over the weekend, see how close I get to fixing hickups up properly. -Mike -- 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] | [next] | [standalone]
| From | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| Date | 2016-01-13 19:00 +0100 |
| Message-ID | <qQxSb-37P-23@gated-at.bofh.it> |
| In reply to | #1299848 |
* Mike Galbraith | 2016-01-01 08:19:41 [+0100]: >> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND >> 3 root -2 0 0 0 0 S 37.3 0.0 307:52.44 ksoftirqd/0 >> 32 root -2 0 0 0 0 S 37.3 0.0 308:08.72 ksoftirqd/2 >> 42 root -2 0 0 0 0 R 37.3 0.0 308:32.84 ksoftirqd/3 >> 22 root -2 0 0 0 0 S 26.9 0.0 222:29.82 ksoftirqd/1 >> 1 root 20 0 46628 6980 4976 S 1.3 0.2 0:13.98 systemd >> 22358 williams 20 0 159980 4552 3780 R 1.0 0.1 0:00.39 top > >Heh, I didn't notice immediately because I throttle nohz, am seeing >only tiny utilization (but nohz idle isn't working). With throttle >patch removed, box is screaming, expires=4294990471 pokes eyeball. This is due to NO_HZ as far as I can tell. My AMD A10 in idle mode has 0.7% utilisation of ksoftirqd/ with CONFIG_HZ_PERIODIC and with CONFIG_NO_HZ_FULL it shows about 25% on all CPU threads. Sebastian
[toc] | [prev] | [next] | [standalone]
| From | Grygorii Strashko <grygorii.strashko@ti.com> |
|---|---|
| Date | 2016-01-13 19:40 +0100 |
| Message-ID | <qQyuS-3Ce-25@gated-at.bofh.it> |
| In reply to | #1308691 |
On 01/13/2016 07:58 PM, Sebastian Andrzej Siewior wrote:
> * Mike Galbraith | 2016-01-01 08:19:41 [+0100]:
>
>>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>>> 3 root -2 0 0 0 0 S 37.3 0.0 307:52.44 ksoftirqd/0
>>> 32 root -2 0 0 0 0 S 37.3 0.0 308:08.72 ksoftirqd/2
>>> 42 root -2 0 0 0 0 R 37.3 0.0 308:32.84 ksoftirqd/3
>>> 22 root -2 0 0 0 0 S 26.9 0.0 222:29.82 ksoftirqd/1
>>> 1 root 20 0 46628 6980 4976 S 1.3 0.2 0:13.98 systemd
>>> 22358 williams 20 0 159980 4552 3780 R 1.0 0.1 0:00.39 top
>>
>> Heh, I didn't notice immediately because I throttle nohz, am seeing
>> only tiny utilization (but nohz idle isn't working). With throttle
>> patch removed, box is screaming, expires=4294990471 pokes eyeball.
>
> This is due to NO_HZ as far as I can tell. My AMD A10 in idle mode has
> 0.7% utilisation of ksoftirqd/ with CONFIG_HZ_PERIODIC and with
> CONFIG_NO_HZ_FULL it shows about 25% on all CPU threads.
>
I might be wrong completely, but could below two patches affect on
CPU utilization of ksoftirqd?
6047967 ksoftirqd: Use new cond_resched_rcu_qs() function
28423ad ksoftirqd: Enable IRQs and call cond_resched() before poking RCU
above two patches are not applied on -RT part of softirqs processing.
static void run_ksoftirqd(unsigned int cpu)
{
local_irq_disable();
current->softirq_nestcnt++;
do_current_softirqs();
current->softirq_nestcnt--;
rcu_note_context_switch();
^^^ IRQs disabled
local_irq_enable();
}
--
regards,
-grygorii
[toc] | [prev] | [next] | [standalone]
| From | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| Date | 2016-01-14 16:00 +0100 |
| Message-ID | <qQRxw-8vf-11@gated-at.bofh.it> |
| In reply to | #1308723 |
* Grygorii Strashko | 2016-01-13 20:36:56 [+0200]: >I might be wrong completely, but could below two patches affect on >CPU utilization of ksoftirqd? > >6047967 ksoftirqd: Use new cond_resched_rcu_qs() function >28423ad ksoftirqd: Enable IRQs and call cond_resched() before poking RCU > >above two patches are not applied on -RT part of softirqs processing. this has been overseen, thanks. Sebastian
[toc] | [prev] | [next] | [standalone]
| From | Mike Galbraith <umgwanakikbuti@gmail.com> |
|---|---|
| Date | 2016-01-14 10:40 +0100 |
| Message-ID | <qQMxQ-54U-3@gated-at.bofh.it> |
| In reply to | #1308691 |
On Wed, 2016-01-13 at 18:58 +0100, Sebastian Andrzej Siewior wrote: > * Mike Galbraith | 2016-01-01 08:19:41 [+0100]: > > > > PID USER PR NI VIRT RES SHR S %CPU %MEM > > > TIME+ COMMAND > > > 3 root -2 0 0 0 0 S 37.3 0.0 > > > 307:52.44 ksoftirqd/0 > > > 32 root -2 0 0 0 0 S 37.3 0.0 > > > 308:08.72 ksoftirqd/2 > > > 42 root -2 0 0 0 0 R 37.3 0.0 > > > 308:32.84 ksoftirqd/3 > > > 22 root -2 0 0 0 0 S 26.9 0.0 > > > 222:29.82 ksoftirqd/1 > > > 1 root 20 0 46628 6980 4976 S 1.3 0.2 > > > 0:13.98 systemd > > > 22358 williams 20 0 159980 4552 3780 R 1.0 0.1 > > > 0:00.39 top > > > > Heh, I didn't notice immediately because I throttle nohz, am seeing > > only tiny utilization (but nohz idle isn't working). With throttle > > patch removed, box is screaming, expires=4294990471 pokes eyeball. > > This is due to NO_HZ as far as I can tell. My AMD A10 in idle mode > has > 0.7% utilisation of ksoftirqd/ with CONFIG_HZ_PERIODIC and with > CONFIG_NO_HZ_FULL it shows about 25% on all CPU threads. Thomas said the hrtimer adjustments went a little out of round. I started rummaging, but then the world woke up from the holidays, so I didn't get _to_ square one, much lest past it. Hohum. -Mike
[toc] | [prev] | [next] | [standalone]
| From | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| Date | 2016-01-14 15:20 +0100 |
| Message-ID | <qQQUO-8fS-5@gated-at.bofh.it> |
| In reply to | #1308691 |
* Sebastian Andrzej Siewior | 2016-01-13 18:58:45 [+0100]:
>This is due to NO_HZ as far as I can tell. My AMD A10 in idle mode has
>0.7% utilisation of ksoftirqd/ with CONFIG_HZ_PERIODIC and with
>CONFIG_NO_HZ_FULL it shows about 25% on all CPU threads.
This should fixed it:
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -1453,7 +1453,7 @@ u64 get_next_timer_interrupt(unsigned long basej, u64 basem)
* the base lock to check when the next timer is pending and so
* we assume the next jiffy.
*/
- return basej;
+ return basem + TICK_NSEC;
#endif
spin_lock(&base->lock);
if (base->active_timers) {
Sebastian
[toc] | [prev] | [next] | [standalone]
| From | Mike Galbraith <umgwanakikbuti@gmail.com> |
|---|---|
| Date | 2016-01-14 15:40 +0100 |
| Message-ID | <qQRe9-8oq-17@gated-at.bofh.it> |
| In reply to | #1309303 |
On Thu, 2016-01-14 at 15:17 +0100, Sebastian Andrzej Siewior wrote:
> * Sebastian Andrzej Siewior | 2016-01-13 18:58:45 [+0100]:
>
> > This is due to NO_HZ as far as I can tell. My AMD A10 in idle mode
> > has
> > 0.7% utilisation of ksoftirqd/ with CONFIG_HZ_PERIODIC and with
> > CONFIG_NO_HZ_FULL it shows about 25% on all CPU threads.
>
> This should fixed it:
>
> --- a/kernel/time/timer.c
> +++ b/kernel/time/timer.c
> @@ -1453,7 +1453,7 @@ u64 get_next_timer_interrupt(unsigned long
> basej, u64 basem)
> * the base lock to check when the next timer is pending and
> so
> * we assume the next jiffy.
> */
> - return basej;
> + return basem + TICK_NSEC;
> #endif
> spin_lock(&base->lock);
> if (base->active_timers) {
That's what I had done to stop the screaming interrupt, but box still
behaved very badly.
-Mike
[toc] | [prev] | [next] | [standalone]
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Date | 2016-01-14 15:40 +0100 |
| Message-ID | <qQRea-8oq-31@gated-at.bofh.it> |
| In reply to | #1309332 |
On Thu, 14 Jan 2016, Mike Galbraith wrote:
> On Thu, 2016-01-14 at 15:17 +0100, Sebastian Andrzej Siewior wrote:
> > * Sebastian Andrzej Siewior | 2016-01-13 18:58:45 [+0100]:
> >
> > > This is due to NO_HZ as far as I can tell. My AMD A10 in idle mode
> > > has
> > > 0.7% utilisation of ksoftirqd/ with CONFIG_HZ_PERIODIC and with
> > > CONFIG_NO_HZ_FULL it shows about 25% on all CPU threads.
> >
> > This should fixed it:
> >
> > --- a/kernel/time/timer.c
> > +++ b/kernel/time/timer.c
> > @@ -1453,7 +1453,7 @@ u64 get_next_timer_interrupt(unsigned long
> > basej, u64 basem)
> > * the base lock to check when the next timer is pending and
> > so
> > * we assume the next jiffy.
> > */
> > - return basej;
> > + return basem + TICK_NSEC;
> > #endif
> > spin_lock(&base->lock);
> > if (base->active_timers) {
>
> That's what I had done to stop the screaming interrupt, but box still
> behaved very badly.
If you turn off CONFIG_NO_HZ_FULL and switch to NO_HZ_IDLE is it still bad?
Thanks,
tglx
[toc] | [prev] | [next] | [standalone]
| From | Mike Galbraith <umgwanakikbuti@gmail.com> |
|---|---|
| Date | 2016-01-14 16:00 +0100 |
| Message-ID | <qQRxx-8vf-39@gated-at.bofh.it> |
| In reply to | #1309336 |
On Thu, 2016-01-14 at 15:30 +0100, Thomas Gleixner wrote:
> On Thu, 14 Jan 2016, Mike Galbraith wrote:
>
> > On Thu, 2016-01-14 at 15:17 +0100, Sebastian Andrzej Siewior wrote:
> > > * Sebastian Andrzej Siewior | 2016-01-13 18:58:45 [+0100]:
> > >
> > > > This is due to NO_HZ as far as I can tell. My AMD A10 in idle
> mode
> > > > has
> > > > 0.7% utilisation of ksoftirqd/ with CONFIG_HZ_PERIODIC and with
> > > > CONFIG_NO_HZ_FULL it shows about 25% on all CPU threads.
> > >
> > > This should fixed it:
> > >
> > > --- a/kernel/time/timer.c
> > > +++ b/kernel/time/timer.c
> > > @@ -1453,7 +1453,7 @@ u64 get_next_timer_interrupt(unsigned long
> > > basej, u64 basem)
> > > * the base lock to check when the next timer is pending and
> > > so
> > > * we assume the next jiffy.
> > > */
> > > - return basej;
> > > + return basem + TICK_NSEC;
> > > #endif
> > > spin_lock(&base->lock);
> > > if (base->active_timers) {
> >
> > That's what I had done to stop the screaming interrupt, but box
> still
> > behaved very badly.
>
> If you turn off CONFIG_NO_HZ_FULL and switch to NO_HZ_IDLE is it
> still bad?
I didn't have CONFIG_NO_HZ_FULL enabled, it was CONFIG_NO_HZ_IDLE.
-Mike
[toc] | [prev] | [next] | [standalone]
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Date | 2016-01-14 16:10 +0100 |
| Message-ID | <qQRHc-nE-11@gated-at.bofh.it> |
| In reply to | #1309360 |
On Thu, 14 Jan 2016, Mike Galbraith wrote:
> On Thu, 2016-01-14 at 15:30 +0100, Thomas Gleixner wrote:
> > On Thu, 14 Jan 2016, Mike Galbraith wrote:
> >
> > > On Thu, 2016-01-14 at 15:17 +0100, Sebastian Andrzej Siewior wrote:
> > > > * Sebastian Andrzej Siewior | 2016-01-13 18:58:45 [+0100]:
> > > >
> > > > > This is due to NO_HZ as far as I can tell. My AMD A10 in idle
> > mode
> > > > > has
> > > > > 0.7% utilisation of ksoftirqd/ with CONFIG_HZ_PERIODIC and with
> > > > > CONFIG_NO_HZ_FULL it shows about 25% on all CPU threads.
> > > >
> > > > This should fixed it:
> > > >
> > > > --- a/kernel/time/timer.c
> > > > +++ b/kernel/time/timer.c
> > > > @@ -1453,7 +1453,7 @@ u64 get_next_timer_interrupt(unsigned long
> > > > basej, u64 basem)
> > > > * the base lock to check when the next timer is pending and
> > > > so
> > > > * we assume the next jiffy.
> > > > */
> > > > - return basej;
> > > > + return basem + TICK_NSEC;
> > > > #endif
> > > > spin_lock(&base->lock);
> > > > if (base->active_timers) {
> > >
> > > That's what I had done to stop the screaming interrupt, but box
> > still
> > > behaved very badly.
> >
> > If you turn off CONFIG_NO_HZ_FULL and switch to NO_HZ_IDLE is it
> > still bad?
>
> I didn't have CONFIG_NO_HZ_FULL enabled, it was CONFIG_NO_HZ_IDLE.
So with the above fix it still behaves badly. Can you provide your config and
a hint which workload/idle/whatever state results in bad behaviour.
Thanks,
tglx
[toc] | [prev] | [next] | [standalone]
| From | Mike Galbraith <umgwanakikbuti@gmail.com> |
|---|---|
| Date | 2016-01-14 17:10 +0100 |
| Message-ID | <qQSDg-10I-3@gated-at.bofh.it> |
| In reply to | #1309364 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, 2016-01-14 at 16:07 +0100, Thomas Gleixner wrote: > > I didn't have CONFIG_NO_HZ_FULL enabled, it was CONFIG_NO_HZ_IDLE. > > So with the above fix it still behaves badly. Can you provide your config and > a hint which workload/idle/whatever state results in bad behaviour. This is virgin -rt1 modulo fixlet applied to v4.4.0, built with the .config from v4.4.0 that built it (modulo RT_FULL) rebuilding itself via make -j8. homer:/root # vmstat 10 procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 0 1 0 14742988 179832 680792 0 0 634 25 326 1196 2 1 89 8 0 8 0 0 14476084 179848 701632 0 0 814 525 2421 12314 11 1 87 1 0 8 0 0 14483232 179864 712656 0 0 165 1628 2404 12320 11 1 87 1 0 8 0 0 14493336 180008 727836 0 0 141 762 2328 11306 11 1 87 0 0 8 0 0 14456436 180024 738356 0 0 159 1478 2336 11939 11 1 87 0 0 Way too idle, taking forever. -Mike
[toc] | [prev] | [next] | [standalone]
| From | Tim Sander <tim@krieglstein.org> |
|---|---|
| Date | 2016-01-07 13:20 +0100 |
| Message-ID | <qOhHQ-7YB-21@gated-at.bofh.it> |
| In reply to | #1297683 |
Hi Sebastian
Thanks for your christmas present :-).
Am Mittwoch, 23. Dezember 2015, 23:57:55 schrieb Sebastian Andrzej Siewior:
> Please don't continue reading before christmas eve (or morning,
> depending on your schedule). If you don't celebrate christmas,
> well go ahead.
Ok, i have to admit i am a little late to the party.
> Dear RT folks!
>
> I'm pleased to announce the v4.4-rc6-rt1 patch set. I tested it on my
> AMD A10, 64bit. Nothing exploded so far, filesystem is still there.
> I haven't tested it on anything else. Before someone asks: this does not
> mean it does *not* work on ARM I simply did not try it.
With the trivial compile patch below it is working on ARM:
Specifically two Cortex A9 on a CycloneV from Altera.
The performance without load looks good:
# Total: 100000000 100000000
# Min Latencies: 00009 00009
# Avg Latencies: 00010 00010
# Max Latencies: 00022 00033
A short run with hackbench load reveals an latency "island" from 54-69µs on the first core.
There are no timer ticks with 34 to 53 µs delay.
# Total: 001000000 000999714
# Min Latencies: 00010 00009
# Avg Latencies: 00017 00010
# Max Latencies: 00069 00029
I will test further and report if i find strange occurences.
> If you are brave then download it, install it and have fun. If something
> breaks, please report it. If your machine starts blinking like a
> christmas tree while using the patch then *please* send a photo.
Sorry no photos, no special blinking.
Best regards
Tim
Signed-off-by: Tim Sander <tim@krieglstein.org>
--- linux-4.4-rc6/kernel/time/hrtimer.c.orig 2016-01-06 16:56:32.573527206 +0100
+++ linux-4.4-rc6/kernel/time/hrtimer.c 2016-01-06 16:56:48.213215320 +0100
@@ -1435,6 +1435,7 @@
#endif
+static enum hrtimer_restart hrtimer_wakeup(struct hrtimer *timer);
static void __hrtimer_run_queues(struct hrtimer_cpu_base *cpu_base, ktime_t now)
{
@@ -1490,8 +1491,6 @@
raise_softirq_irqoff(HRTIMER_SOFTIRQ);
}
-static enum hrtimer_restart hrtimer_wakeup(struct hrtimer *timer);
-
#ifdef CONFIG_HIGH_RES_TIMERS
/*
--
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] | [next] | [standalone]
| From | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| Date | 2016-01-13 14:50 +0100 |
| Message-ID | <qQtYe-s0-17@gated-at.bofh.it> |
| In reply to | #1303529 |
* Tim Sander | 2016-01-07 13:15:33 [+0100]: >Signed-off-by: Tim Sander <tim@krieglstein.org> Thanks for the report. Sebastian
[toc] | [prev] | [next] | [standalone]
| From | "Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com> |
|---|---|
| Date | 2016-01-13 12:50 +0100 |
| Subject | Re: [ANNOUNCE] 4.4-rc6-rt1 (arm64) |
| Message-ID | <qQs66-7xx-21@gated-at.bofh.it> |
| In reply to | #1297683 |
Hi All,
I am trying to boot linux kernel 4.4.rc7 with the 4.4-rc6-rt1 patch on Cavium thunderX arm64 platform
Below is the bootlog with errors.
......
ata4: SATA link down (SStatus 0 SControl 300)
ata2: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata1.00: ATA-8: WDC WD5003ABYZ-011FA0, 01.01S03, max UDMA/133
ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA WDC WD5003ABYZ-0 1S03 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem
sched: RT throttling activated
NOHZ: local_softirq_pending 02
NOHZ: local_softirq_pending 82
NOHZ: local_softirq_pending 82
NOHZ: local_softirq_pending 82
NOHZ: local_softirq_pending 82
NOHZ: local_softirq_pending 82
NOHZ: local_softirq_pending 82
NOHZ: local_softirq_pending 82
NOHZ: local_softirq_pending 82
NOHZ: local_softirq_pending 82
ata1.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x6 frozen
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/08:70:00:08:20/00:00:00:00:00/40 tag 14 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.00: revalidation failed (errno=-5)
ata1: hard resetting link
ata1.00: qc timeout (cmd 0xec)
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.00: revalidation failed (errno=-5)
ata1.00: disabled
ata1.00: device reported invalid CHS sector 0
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
ata1: EH complete
sd 0:0:0:0: [sda] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
sd 0:0:0:0: [sda] tag#16 CDB: opcode=0x28 28 00 00 20 08 00 00 00 08 00
blk_update_request: I/O error, dev sda, sector 2099200
EXT4-fs (sda2): Can't read superblock on 2nd try
sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x28 28 00 00 20 08 02 00 00 02 00
blk_update_request: I/O error, dev sda, sector 2099202
EXT4-fs (sda2): unable to read superblock
sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x28 28 00 00 20 08 02 00 00 02 00
blk_update_request: I/O error, dev sda, sector 2099202
EXT2-fs (sda2): error: unable to read superblock
sd 0:0:0:0: [sda] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
sd 0:0:0:0: [sda] tag#22 CDB: opcode=0x28 28 00 00 20 08 00 00 00 01 00
blk_update_request: I/O error, dev sda, sector 2099200
FAT-fs (sda2): unable to read boot sector
VFS: Cannot open root device "sda2" or unknown-block(8,2): error -5
Please append a correct "root=" boot option; here are the available partitions:
0800 488386584 sda driver: sd
0801 1048576 sda1 60ff81a8-b24d-49ac-bcf4-c8dd8fc66cba
0802 33800192 sda2 7549f29b-11b1-4284-9d21-efd6a9d8dfc1
0803 453536768 sda3 92c94e3c-2c71-4e1b-82d4-804bb7a68b8a
0802 33800192 sda2 7549f29b-11b1-4284-9d21-efd6a9d8dfc1
0803 453536768 sda3 92c94e3c-2c71-4e1b-82d4-804bb7a68b8a
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.0-rc7-rt1+ #11Call trace:
[<fffffe0000096a3c>] dump_backtrace+0x0/0x11c
[<fffffe0000096b6c>] show_stack+0x14/0x1c
[<fffffe000030a37c>] dump_stack+0x88/0xa8
[<fffffe000014be34>] panic+0xf0/0x23c
[<fffffe0000850ec4>] mount_block_root+0x1b8/0x25c
[<fffffe0000851090>] mount_root+0x128/0x144
[<fffffe00008511e8>] prepare_namespace+0x13c/0x184
[<fffffe0000850b54>] kernel_init_freeable+0x1d0/0x1f4
[<fffffe00005c7524>] kernel_init+0x10/0xd8
[<fffffe0000093980>] ret_from_fork+0x10/0x50
CPU2: stopping
[toc] | [prev] | [next] | [standalone]
| From | Sebastian Andrzej Siewior <bigeasy@linutronix.de> |
|---|---|
| Date | 2016-01-13 14:50 +0100 |
| Subject | Re: [ANNOUNCE] 4.4-rc6-rt1 (arm64) |
| Message-ID | <qQtYf-s0-25@gated-at.bofh.it> |
| In reply to | #1308320 |
* Jaggi, Manish | 2016-01-13 11:45:54 [+0000]: >Hi All, > >I am trying to boot linux kernel 4.4.rc7 with the 4.4-rc6-rt1 patch on Cavium thunderX arm64 platform >Below is the bootlog with errors. This and your previous email look the same to me. Did v4.1-RT work here? Can you enable some debuging in order to figure out what triggers "RT throttling activated"? lockdep, sleeping while atomic, the usual stuff :) > Sebastian
[toc] | [prev] | [next] | [standalone]
| From | "Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com> |
|---|---|
| Date | 2016-01-14 13:00 +0100 |
| Subject | Re: [ANNOUNCE] 4.4-rc6-rt1 (arm64) |
| Message-ID | <qQOJk-6rt-13@gated-at.bofh.it> |
| In reply to | #1308425 |
Hi Sebastian , One quick point, I disabled the hr timer from kernel config and I was able to boot kernel. Regards, Manish Jaggi ________________________________________ From: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Sent: Wednesday, January 13, 2016 7:15 PM To: Jaggi, Manish Cc: Mike Galbraith; Clark Williams; Thomas Gleixner; LKML; linux-rt-users; Steven Rostedt Subject: Re: [ANNOUNCE] 4.4-rc6-rt1 (arm64) * Jaggi, Manish | 2016-01-13 11:45:54 [+0000]: >Hi All, > >I am trying to boot linux kernel 4.4.rc7 with the 4.4-rc6-rt1 patch on Cavium thunderX arm64 platform >Below is the bootlog with errors. This and your previous email look the same to me. Did v4.1-RT work here? Can you enable some debuging in order to figure out what triggers "RT throttling activated"? lockdep, sleeping while atomic, the usual stuff :) > Sebastian
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web