[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090105043006.GA22049@linux.vnet.ibm.com>
Date: Sun, 4 Jan 2009 20:30:06 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: linux-kernel@...r.kernel.org
Cc: mingo@...e.hu, andi@...stfloor.org, snakebyte@....de,
akpm@...ux-foundation.org, dvhltc@...ibm.com, niv@...ibm.com,
manfred@...orfullife.com, laijs@...fujitsu.com
Subject: [PATCH] Fix rcutree grace-period-latency bug on small systems
Kudos to Andi Kleen for finding a grace-period-latency problem! The
problem was that the special-case code for small machines never updated
the ->signaled field to indicate that grace-period initialization had
completed, which prevented force_quiescent_state() from ever expediting
grace periods. This problem resulted in grace periods extending for more
than 20 seconds. Not subtle. I introduced this bug during my inspection
process when I fixed a race between grace-period initialization and
force_quiescent_state() execution.
The following patch properly updates the ->signaled field for the
"small"-system case (no more than 32 CPUs for 32-bit kernels and no more
than 64 CPUs for 64-bit kernels).
I believe that this patch should be included for 2.6.29.
Located-by: Andi Kleen <andi@...stfloor.org>
Tested-by: Andi Kleen <andi@...stfloor.org>
Signed-off-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
---
rcutree.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/rcutree.c b/kernel/rcutree.c
index a342b03..88d921c 100644
--- a/kernel/rcutree.c
+++ b/kernel/rcutree.c
@@ -572,6 +572,7 @@ rcu_start_gp(struct rcu_state *rsp, unsigned long flags)
/* Special-case the common single-level case. */
if (NUM_RCU_NODES == 1) {
rnp->qsmask = rnp->qsmaskinit;
+ rsp->signaled = RCU_SIGNAL_INIT; /* force_quiescent_state OK. */
spin_unlock_irqrestore(&rnp->lock, flags);
return;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists