From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756209Ab0KXAb3 (ORCPT ); Tue, 23 Nov 2010 19:31:29 -0500 Received: from mail-fx0-f46.google.com ([209.85.161.46]:53469 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756017Ab0KXAb0 (ORCPT ); Tue, 23 Nov 2010 19:31:26 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:x-mailer:in-reply-to:references; b=EwePUR6HzS8wgsTDob1XGhwy92mlk7KWN2nMYW4fkgSCr7kHi6ID0g+FVf74b8mUy9 tvifAHX9avwtpMU2UM6BRNggnp+4d7dTd68NrsBCqCopOKaLePNXK2QY1PioLQcL66Yo aMCcTPIBOGlOkyEfsd3Q600k5EaG9jd7viUQA= From: Frederic Weisbecker To: "Paul E. McKenney" Cc: LKML , Frederic Weisbecker , "Paul E. McKenney" , Lai Jiangshan , Ingo Molnar , Thomas Gleixner , Peter Zijlstra , Steven Rostedt Subject: [PATCH 2/2] rcu: Stop checking quiescent states after grace period completion from remote Date: Wed, 24 Nov 2010 01:31:13 +0100 Message-Id: <1290558673-23580-3-git-send-crap-fweisbec@gmail.com> X-Mailer: git-send-email 1.7.3.2 In-Reply-To: <1290558673-23580-1-git-send-crap-fweisbec@gmail.com> References: <1290558673-23580-1-git-send-crap-fweisbec@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org After a CPU starts to chase its quiescent states by setting rdp->qs_pending to 1, it can still enter into an extended quiescent state and then another CPU will take care of this and complete the grace period if necessary. rcu_report_qs_rdp() currently doesn't handle well this case and considers it must try later to notify its quiescent state. However if the last grace period has been completed there is nothing left to do for the current CPU. It means that until a next grace period starts, the CPU that runs into that case will keep chasing its own quiescent states by raising a softirq on every tick for no good reason. This can take a while before a new grace period starts and this time slice is covered by spurious softirqs and other kinds of rcu checks. Fix this by resetting rdp->qs_pending if the last grace period has been completed by a remote CPU while we were in an extended quiescent state. Signed-off-by: Frederic Weisbecker Cc: Paul E. McKenney Cc: Lai Jiangshan Cc: Ingo Molnar Cc: Thomas Gleixner Cc: Peter Zijlstra Cc: Steven Rostedt --- kernel/rcutree.c | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/kernel/rcutree.c b/kernel/rcutree.c index 5f038a1..f287eaa 100644 --- a/kernel/rcutree.c +++ b/kernel/rcutree.c @@ -937,6 +937,15 @@ rcu_report_qs_rdp(int cpu, struct rcu_state *rsp, struct rcu_data *rdp, long las * race occurred. */ rdp->passed_quiesc = 0; /* try again later! */ + + /* + * Another CPU may have taken care of us if we were in an + * extended quiescent state, in which case we don't need + * to continue to track anything. + */ + if (rnp->gpnum == rnp->completed) + rdp->qs_pending = 0; + raw_spin_unlock_irqrestore(&rnp->lock, flags); return; } -- 1.7.1