Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753683Ab3DMOHB (ORCPT ); Sat, 13 Apr 2013 10:07:01 -0400 Received: from mail-la0-f41.google.com ([209.85.215.41]:38378 "EHLO mail-la0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753311Ab3DMOHA (ORCPT ); Sat, 13 Apr 2013 10:07:00 -0400 MIME-Version: 1.0 In-Reply-To: <1365808754-20762-3-git-send-email-paulmck@linux.vnet.ibm.com> References: <20130412231846.GA20038@linux.vnet.ibm.com> <1365808754-20762-1-git-send-email-paulmck@linux.vnet.ibm.com> <1365808754-20762-3-git-send-email-paulmck@linux.vnet.ibm.com> Date: Sat, 13 Apr 2013 16:06:58 +0200 Message-ID: Subject: Re: [PATCH tip/core/rcu 3/7] rcu: Kick adaptive-ticks CPUs that are holding up RCU grace periods From: Frederic Weisbecker To: "Paul E. McKenney" Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com, akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca, josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org, Valdis.Kletnieks@vt.edu, dhowells@redhat.com, edumazet@google.com, darren@dvhart.com, sbw@mit.edu Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1547 Lines: 31 2013/4/13 Paul E. McKenney : > From: "Paul E. McKenney" > > Adaptive-ticks CPUs inform RCU when they enter kernel mode, but they do > not necessarily turn the scheduler-clock tick back on. This state of > affairs could result in RCU waiting on an adaptive-ticks CPU running > for an extended period in kernel mode. Such a CPU will never run the > RCU state machine, and could therefore indefinitely extend the RCU state > machine, sooner or later resulting in an OOM condition. > > This patch, inspired by an earlier patch by Frederic Weisbecker, therefore > causes RCU's force-quiescent-state processing to check for this condition > and to send an IPI to CPUs that remain in that state for too long. > "Too long" currently means about three jiffies by default, which is > quite some time for a CPU to remain in the kernel without blocking. > The rcu_tree.jiffies_till_first_fqs and rcutree.jiffies_till_next_fqs > sysfs variables may be used to tune "too long" if needed. > > Reported-by: Frederic Weisbecker > Signed-off-by: Paul E. McKenney It might be better if I take this patch to get it through tip:timers/nohz so that I can keep it in sync with the rest. What do you think? Thanks. -- 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/