Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754509AbbGBCu4 (ORCPT ); Wed, 1 Jul 2015 22:50:56 -0400 Received: from mail-wg0-f45.google.com ([74.125.82.45]:35346 "EHLO mail-wg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753302AbbGBCus (ORCPT ); Wed, 1 Jul 2015 22:50:48 -0400 Message-ID: <1435805445.6887.50.camel@gmail.com> Subject: Re: [PATCH RFC tip/core/rcu 0/5] Expedited grace periods encouraging normal ones From: Mike Galbraith To: paulmck@linux.vnet.ibm.com Cc: josh@joshtriplett.org, Peter Zijlstra , linux-kernel@vger.kernel.org, mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com, akpm@linux-foundation.org, mathieu.desnoyers@efficios.com, tglx@linutronix.de, rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com Date: Thu, 02 Jul 2015 04:50:45 +0200 In-Reply-To: <20150702021838.GA3717@linux.vnet.ibm.com> References: <20150630221224.GQ3717@linux.vnet.ibm.com> <20150630234633.GA11450@cloud> <20150701100939.GR19282@twins.programming.kicks-ass.net> <20150701105511.GN18673@twins.programming.kicks-ass.net> <20150701140031.GB3717@linux.vnet.ibm.com> <20150701141710.GG25159@twins.programming.kicks-ass.net> <20150701161705.GK3717@linux.vnet.ibm.com> <1435799484.3482.15.camel@gmail.com> <20150702013426.GB19350@cloud> <1435802395.6887.20.camel@gmail.com> <20150702021838.GA3717@linux.vnet.ibm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 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 Content-Length: 865 Lines: 20 On Wed, 2015-07-01 at 19:18 -0700, Paul E. McKenney wrote: > Does their normal workload trigger the condition that results in the > expedited grace period? If so, do they use NO_HZ_FULL? They're having no trouble that I'm aware of, and I definitely would be made aware. They're not currently using a kernel with NO_HZ_FULL even built in, as that stuff is far far too raw in the current kernel. They may meet a NO_HZ_FULL enabled kernel soonish, but will be told to not turn it on for anything other than pure compute, as NO_HZ_FULL is currently not usable for mixed load in partitioned box, much less rt. -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/