Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751917AbaFDTo4 (ORCPT ); Wed, 4 Jun 2014 15:44:56 -0400 Received: from g4t3426.houston.hp.com ([15.201.208.54]:59283 "EHLO g4t3426.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750780AbaFDToz (ORCPT ); Wed, 4 Jun 2014 15:44:55 -0400 Message-ID: <1401911076.13877.4.camel@buesod1.americas.hpqcorp.net> Subject: Re: [PATCH v2] rwsem: Support optimistic spinning From: Davidlohr Bueso To: Andev Cc: paulmck@linux.vnet.ibm.com, Tim Chen , Ingo Molnar , Andrew Morton , Linus Torvalds , Peter Zijlstra , Andrea Arcangeli , Alex Shi , Andi Kleen , Michel Lespinasse , Rik van Riel , Peter Hurley , Thomas Gleixner , Aswin Chandramouleeswaran , "Norton, Scott J" , LKML Date: Wed, 04 Jun 2014 12:44:36 -0700 In-Reply-To: References: <1398205166.6345.7.camel@buesod1.americas.hpqcorp.net> <1398722941.25549.16.camel@buesod1.americas.hpqcorp.net> <20140428231002.GO4430@linux.vnet.ibm.com> <1398732649.2970.89.camel@schen9-DESK> <20140429151100.GC8754@linux.vnet.ibm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4 (3.6.4-3.fc18) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2014-06-04 at 13:57 -0400, Andev wrote: > Hi, > > On Tue, Apr 29, 2014 at 11:11 AM, Paul E. McKenney > wrote: > > On Mon, Apr 28, 2014 at 05:50:49PM -0700, Tim Chen wrote: > >> On Mon, 2014-04-28 at 16:10 -0700, Paul E. McKenney wrote: > >> > >> > > +#ifdef CONFIG_SMP > >> > > +static inline bool rwsem_can_spin_on_owner(struct rw_semaphore *sem) > >> > > +{ > >> > > + int retval; > >> > > + struct task_struct *owner; > >> > > + > >> > > + rcu_read_lock(); > >> > > + owner = ACCESS_ONCE(sem->owner); > >> > > >> > OK, I'll bite... > >> > > >> > Why ACCESS_ONCE() instead of rcu_dereference()? > >> > >> We're using it as a speculative check on the sem->owner to see > >> if the owner is running on the cpu. The rcu_read_lock > >> is used for ensuring that the owner->on_cpu memory is > >> still valid. > > > > OK, so if we read complete garbage, all that happens is that we > > lose a bit of performance? If so, I am OK with it as long as there > > is a comment (which Davidlohr suggested later in this thread). > > > > Thanx, Paul > > > > The latest code seems to be missing this comment. Could you please add this? The comment is there when we declare ->owner in struct rw_semaphore. -- 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/