From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753724AbcANO5J (ORCPT ); Thu, 14 Jan 2016 09:57:09 -0500 Received: from mail-wm0-f49.google.com ([74.125.82.49]:34069 "EHLO mail-wm0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751154AbcANO5H (ORCPT ); Thu, 14 Jan 2016 09:57:07 -0500 Message-ID: <1452783422.3611.8.camel@gmail.com> Subject: Re: [ANNOUNCE] 4.4-rc6-rt1 From: Mike Galbraith To: Thomas Gleixner Cc: Sebastian Andrzej Siewior , Clark Williams , LKML , linux-rt-users , Steven Rostedt Date: Thu, 14 Jan 2016 15:57:02 +0100 In-Reply-To: References: <20151223225755.GA21121@linutronix.de> <20151231102441.581ce1e1@sluggy.hsv.redhat.com> <1451632781.9800.22.camel@gmail.com> <20160113175845.GK29964@linutronix.de> <20160114141744.GB17776@linutronix.de> <1452781751.3460.102.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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