Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754206AbaDRQ0q (ORCPT ); Fri, 18 Apr 2014 12:26:46 -0400 Received: from g4t3426.houston.hp.com ([15.201.208.54]:29285 "EHLO g4t3426.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751205AbaDRQ0n (ORCPT ); Fri, 18 Apr 2014 12:26:43 -0400 Message-ID: <53515232.50905@hp.com> Date: Fri, 18 Apr 2014 12:26:26 -0400 From: Waiman Long User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: Ingo Molnar CC: Peter Zijlstra , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , linux-arch@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, xen-devel@lists.xenproject.org, kvm@vger.kernel.org, Paolo Bonzini , Konrad Rzeszutek Wilk , "Paul E. McKenney" , Rik van Riel , Linus Torvalds , Raghavendra K T , David Vrabel , Oleg Nesterov , Gleb Natapov , Scott J Norton , Chegu Vinod Subject: Re: [PATCH v9 05/19] qspinlock: Optimize for smaller NR_CPUS References: <1397747051-15401-1-git-send-email-Waiman.Long@hp.com> <1397747051-15401-6-git-send-email-Waiman.Long@hp.com> <20140417155844.GS11096@twins.programming.kicks-ass.net> <53504C4E.8060800@hp.com> <20140418074616.GB13517@gmail.com> In-Reply-To: <20140418074616.GB13517@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/18/2014 03:46 AM, Ingo Molnar wrote: > * Waiman Long wrote: > >> On 04/17/2014 11:58 AM, Peter Zijlstra wrote: >>> On Thu, Apr 17, 2014 at 11:03:57AM -0400, Waiman Long wrote: >>>> +static __always_inline void >>>> +clear_pending_set_locked(struct qspinlock *lock, u32 val) >>>> +{ >>>> + struct __qspinlock *l = (void *)lock; >>>> + >>>> + ACCESS_ONCE(l->locked_pending) = 1; >>>> +} >>>> @@ -157,8 +251,13 @@ static inline int trylock_pending(struct qspinlock *lock, u32 *pval) >>>> * we're pending, wait for the owner to go away. >>>> * >>>> * *,1,1 -> *,1,0 >>>> + * >>>> + * this wait loop must be a load-acquire such that we match the >>>> + * store-release that clears the locked bit and create lock >>>> + * sequentiality; this because not all try_clear_pending_set_locked() >>>> + * implementations imply full barriers. >>> You renamed the function referred in the above comment. >>> >> Sorry, will fix the comments. > I suggest not renaming the function instead. > try_clear_pending_set_locked() tells the intent in a clearer fashion. > > Thanks, > > Ingo I usually use the word "try" if there is a possibility of failure. However, the function will always succeed, albeit by waiting a bit in some cases. That is why I remove "try" from the name. -Longman -- 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/