From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751685AbbGBSgK (ORCPT ); Thu, 2 Jul 2015 14:36:10 -0400 Received: from mail-wi0-f174.google.com ([209.85.212.174]:33850 "EHLO mail-wi0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754329AbbGBSgD (ORCPT ); Thu, 2 Jul 2015 14:36:03 -0400 Date: Thu, 2 Jul 2015 20:35:57 +0200 From: Ingo Molnar To: "Paul E. McKenney" Cc: Peter Zijlstra , josh@joshtriplett.org, linux-kernel@vger.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 Subject: Re: [PATCH RFC tip/core/rcu 0/5] Expedited grace periods encouraging normal ones Message-ID: <20150702183557.GA15331@gmail.com> References: <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> <20150701170242.GL3644@twins.programming.kicks-ass.net> <20150701200936.GP3717@linux.vnet.ibm.com> <20150702074719.GA27230@gmail.com> <20150702135834.GF3717@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150702135834.GF3717@linux.vnet.ibm.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 * Paul E. McKenney wrote: > > And it's not like it's that hard to stem the flow of algorithmic sloppiness at > > the source, right? > > OK, first let me make sure that I understand what you are asking for: > > 1. Completely eliminate synchronize_rcu_expedited() and > synchronize_sched_expedited(), replacing all uses with their > unexpedited counterparts. (Note that synchronize_srcu_expedited() > does not wake up CPUs, courtesy of its read-side memory barriers.) > The fast-boot guys are probably going to complain, along with > the networking guys. > > 2. Keep synchronize_rcu_expedited() and synchronize_sched_expedited(), > but push back hard on any new uses and question any existing uses. > > 3. Revert 74b51ee152b6 ("ACPI / osl: speedup grace period in > acpi_os_map_cleanup"). > > 4. Something else? I'd love to have 1) but 2) would be a realistic second best option? ;-) Thanks, Ingo