Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752878AbaDWXsp (ORCPT ); Wed, 23 Apr 2014 19:48:45 -0400 Received: from g6t1526.atlanta.hp.com ([15.193.200.69]:34863 "EHLO g6t1526.atlanta.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752681AbaDWXsm (ORCPT ); Wed, 23 Apr 2014 19:48:42 -0400 Message-ID: <53585144.4070309@hp.com> Date: Wed, 23 Apr 2014 19:48:20 -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: Konrad Rzeszutek Wilk 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 , "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-6-git-send-email-Waiman.Long@hp.com> <20140417155649.GR11096@twins.programming.kicks-ass.net> <53504BB3.4010009@hp.com> <20140418082716.GZ11096@twins.programming.kicks-ass.net> <53516672.3010701@hp.com> <20140418190519.GA11182@twins.programming.kicks-ass.net> <53519BBF.7060506@hp.com> <5357CCEF.2000606@hp.com> <20140423145649.GE2777@phenom.dumpdata.com> <5357FBDE.4040400@hp.com> <20140423175535.GB11152@phenom.dumpdata.com> <53583DA8.4030901@hp.com> In-Reply-To: <53583DA8.4030901@hp.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/23/2014 06:24 PM, Waiman Long wrote: > On 04/23/2014 01:55 PM, Konrad Rzeszutek Wilk wrote: >> On Wed, Apr 23, 2014 at 01:43:58PM -0400, Waiman Long wrote: >>> On 04/23/2014 10:56 AM, Konrad Rzeszutek Wilk wrote: >>>> On Wed, Apr 23, 2014 at 10:23:43AM -0400, Waiman Long wrote: >>>>> On 04/18/2014 05:40 PM, Waiman Long wrote: >>>>>> On 04/18/2014 03:05 PM, Peter Zijlstra wrote: >>>>>>> On Fri, Apr 18, 2014 at 01:52:50PM -0400, Waiman Long wrote: >>>>>>>> I am confused by your notation. >>>>>>> Nah, I think I was confused :-) Make the 1 _Q_LOCKED_VAL though, as >>>>>>> that's the proper constant to use. >>>>>> Everyone gets confused once in a while:-) I have plenty of that >>>>>> myself. >>>>>> >>>>>> I will change 1 to _Q_LOCKED_VAL as suggested. >>>>>> >>>>>> -Longman >>>>> The attached patch file contains the additional changes that I had >>>>> made to qspinlock.c file so far. Please let me know if you or others >>>>> have any additional feedbacks or changes that will need to go to the >>>>> next version of the patch series. >>>>> >>>>> I am going to take vacation starting from tomorrow and will be back >>>>> on 5/5 (Mon). So I will not be able to respond to emails within this >>>>> period. >>>>> >>>>> BTW, is there any chance that this patch can be merged to 3.16? >>>> Um, it needs to have Acks from KVM and Xen maintainers who have not >>>> done so. Also Peter needs to chime in. (BTW, please CC >>>> xen-devel@lists.xenproject.org next time you post so that David and >>>> Boris >>>> can take a peek at it). >>> I will cc xen-devel@lists.xenproject.org when I sent out the next >>> patch. >>> >>>> I would strongly recommend you put all your patches on github (free >>>> git >>>> service) so that we can test it and poke it at during your vacation >>>> (and even after). >>>> >>> I am not used to setting up a public repo in github. If I create a >>> repo there, should I put a snapshot of the whole kernel source tree >>> or just a portion of the relevant files as the base? With the later, >>> it won't be buildable. >> You just push your local branch. It should look like a normal >> Linux tree with your commits on top. > > I will try that with my next version. > I have just pushed my git repo out to https://github.com/longman88/kernel-qspinlock. -Longman > -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/ -- 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/