From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754648Ab2BCEXm (ORCPT ); Thu, 2 Feb 2012 23:23:42 -0500 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:48426 "EHLO relay3-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752893Ab2BCEXl (ORCPT ); Thu, 2 Feb 2012 23:23:41 -0500 X-Originating-IP: 217.70.178.144 X-Originating-IP: 50.43.15.19 Date: Thu, 2 Feb 2012 20:23:25 -0800 From: Josh Triplett 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, niv@us.ibm.com, tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org, Valdis.Kletnieks@vt.edu, dhowells@redhat.com, eric.dumazet@gmail.com, darren@dvhart.com, fweisbec@gmail.com, patches@linaro.org, "Paul E. McKenney" Subject: Re: [PATCH RFC tip/core/rcu 22/41] rcu: Simplify unboosting checks Message-ID: <20120203042325.GB3008@leaf> References: <20120201194131.GA10028@linux.vnet.ibm.com> <1328125319-5205-1-git-send-email-paulmck@linux.vnet.ibm.com> <1328125319-5205-22-git-send-email-paulmck@linux.vnet.ibm.com> <20120202023847.GO29058@leaf> <20120202174812.GT2518@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120202174812.GT2518@linux.vnet.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 02, 2012 at 09:48:12AM -0800, Paul E. McKenney wrote: > On Wed, Feb 01, 2012 at 06:38:47PM -0800, Josh Triplett wrote: > > On Wed, Feb 01, 2012 at 11:41:40AM -0800, Paul E. McKenney wrote: > > > From: "Paul E. McKenney" > > > > > > This is a port of commit #82e78d80 from TREE_PREEMPT_RCU to > > > TINY_PREEMPT_RCU. > > > > > > This commit uses the fact that current->rcu_boost_mutex is set > > > any time that the RCU_READ_UNLOCK_BOOSTED flag is set in the > > > current->rcu_read_unlock_special bitmask. This allows tests of > > > the bit to be changed to tests of the pointer, which in turn allows > > > the RCU_READ_UNLOCK_BOOSTED flag to be eliminated. > > > > Does this change affect rcu_read_unlock()'s logic to trigger the > > slowpath only when special flags get set? > > Interestingly enough, it does not. The only way a task can be subjected > to RCU priority boosting is for that task to block sometime in its > current RCU read-side critical section. When the task blocks, the > RCU_READ_UNLOCK_BLOCKED flag will be set. Therefore, any time that the > current->rcu_boost_mutex pointer is non-NULL, the RCU_READ_UNLOCK_BLOCKED > flag will be set, so the current test of current->rcu_read_unlock_special > against zero continues to work correctly. Makes sense; no sense boosting an RCU reader that already has a CPU to run on. > OK, OK, I will update the commit message with words to this effect. ;-) Thanks. :) - Josh Triplett