Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751604AbbEBRpf (ORCPT ); Sat, 2 May 2015 13:45:35 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:43534 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751153AbbEBRpe (ORCPT ); Sat, 2 May 2015 13:45:34 -0400 Date: Sat, 2 May 2015 19:45:03 +0200 From: Greg Kroah-Hartman To: Mike Galbraith Cc: Josh Hunt , LKML , stable , Calvin Owens , "Paul E. McKenney" Subject: Re: [PATCH 3.19 016/175] ksoftirqd: Enable IRQs and call cond_resched() before poking RCU Message-ID: <20150502174503.GA15301@kroah.com> References: <20150304061026.134125919@linuxfoundation.org> <20150304061029.058110661@linuxfoundation.org> <20150501205205.GC2265@kroah.com> <1430536490.3137.30.camel@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1430536490.3137.30.camel@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3357 Lines: 83 On Sat, May 02, 2015 at 05:14:50AM +0200, Mike Galbraith wrote: > On Fri, 2015-05-01 at 22:52 +0200, Greg Kroah-Hartman wrote: > > On Fri, May 01, 2015 at 03:00:00PM -0500, Josh Hunt wrote: > > > On Wed, Mar 4, 2015 at 12:13 AM, Greg Kroah-Hartman > > > wrote: > > > > 3.19-stable review patch. If anyone has any objections, please let me know. > > > > > > > > ------------------ > > > > > > > > From: Calvin Owens > > > > > > > > commit 28423ad283d5348793b0c45cc9b1af058e776fd6 upstream. > > > > > > > > While debugging an issue with excessive softirq usage, I encountered the > > > > following note in commit 3e339b5dae24a706 ("softirq: Use hotplug thread > > > > infrastructure"): > > > > > > > > [ paulmck: Call rcu_note_context_switch() with interrupts enabled. ] > > > > > > > > ...but despite this note, the patch still calls RCU with IRQs disabled. > > > > > > > > This seemingly innocuous change caused a significant regression in softirq > > > > CPU usage on the sending side of a large TCP transfer (~1 GB/s): when > > > > introducing 0.01% packet loss, the softirq usage would jump to around 25%, > > > > spiking as high as 50%. Before the change, the usage would never exceed 5%. > > > > > > > > Moving the call to rcu_note_context_switch() after the cond_sched() call, > > > > as it was originally before the hotplug patch, completely eliminated this > > > > problem. > > > > > > > > Signed-off-by: Calvin Owens > > > > Signed-off-by: Paul E. McKenney > > > > Signed-off-by: Greg Kroah-Hartman > > > > > > > > --- > > > > kernel/softirq.c | 6 +++++- > > > > 1 file changed, 5 insertions(+), 1 deletion(-) > > > > > > > > --- a/kernel/softirq.c > > > > +++ b/kernel/softirq.c > > > > @@ -656,9 +656,13 @@ static void run_ksoftirqd(unsigned int c > > > > * in the task stack here. > > > > */ > > > > __do_softirq(); > > > > - rcu_note_context_switch(); > > > > local_irq_enable(); > > > > cond_resched(); > > > > + > > > > + preempt_disable(); > > > > + rcu_note_context_switch(); > > > > + preempt_enable(); > > > > + > > > > return; > > > > } > > > > local_irq_enable(); > > > > > > > > > > > > -- > > > > 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/ > > > > > > Sorry for the delay in noticing this, but should this be applied to > > > 3.14-stable as well? > > > > Why should it? > > The regression inducing change arrived in 3.7-rc1. > > > And odds are, if I didn't apply it there, it was either > > because it didn't apply, or it broke the build. > > a. [x] rcu_note_context_switch(cpu) -> rcu_note_context_switch() Thanks for this, now applied. greg k-h -- 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/