Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932910AbbELNIc (ORCPT ); Tue, 12 May 2015 09:08:32 -0400 Received: from e31.co.us.ibm.com ([32.97.110.149]:39954 "EHLO e31.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932339AbbELNIa (ORCPT ); Tue, 12 May 2015 09:08:30 -0400 Date: Tue, 12 May 2015 06:08:24 -0700 From: "Paul E. McKenney" To: Peter Zijlstra Cc: Chris Metcalf , Mike Galbraith , Gilad Ben Yossef , Steven Rostedt , Ingo Molnar , Andrew Morton , Rik van Riel , Tejun Heo , Frederic Weisbecker , Christoph Lameter , linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/6] dataplane nohz: run softirqs synchronously on user entry Message-ID: <20150512130824.GI6776@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <1431107927-13998-1-git-send-email-cmetcalf@ezchip.com> <1431107927-13998-4-git-send-email-cmetcalf@ezchip.com> <1431155043.3209.125.camel@gmail.com> <55510D5C.60605@ezchip.com> <20150512093202.GG21418@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150512093202.GG21418@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15051213-8236-0000-0000-00000B69CDEE Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 975 Lines: 25 On Tue, May 12, 2015 at 11:32:02AM +0200, Peter Zijlstra wrote: > On Mon, May 11, 2015 at 04:13:16PM -0400, Chris Metcalf wrote: > > The thing you want to avoid is having two processes both > > runnable at once > > Right, because as soon as nr_running > 1 we kill the entire nohz_full > thing. RT or not for ksoftirqd doesn't matter. > > Then again, like interrupts, you basically want to avoid softirqs in > this mode. > > So I think the right solution is to figure out why the softirqs get > raised and cure that. Makes sense, but it also makes sense to have something that detects when that cure fails and clean up. And, in a test/debug environment, also issuing some sort of diagnostic in that case. Thanx, Paul -- 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/