Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756756Ab3H3QMc (ORCPT ); Fri, 30 Aug 2013 12:12:32 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:9169 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755146Ab3H3QMa (ORCPT ); Fri, 30 Aug 2013 12:12:30 -0400 X-Authority-Analysis: v=2.0 cv=DqnUCRD+ c=1 sm=0 a=Sro2XwOs0tJUSHxCKfOySw==:17 a=Drc5e87SC40A:10 a=_W9BnI6ACgIA:10 a=5SG0PmZfjMsA:10 a=kj9zAlcOel0A:10 a=meVymXHHAAAA:8 a=KGjhK52YXX0A:10 a=4fJcwidASCIA:10 a=pGLkceISAAAA:8 a=B9FaWcOMTwGmGijUrVYA:9 a=CjuIK1q_8ugA:10 a=MSl-tDqOz04A:10 a=Sro2XwOs0tJUSHxCKfOySw==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 67.255.60.225 Date: Fri, 30 Aug 2013 12:12:27 -0400 From: Steven Rostedt To: sedat.dilek@gmail.com Cc: Linus Torvalds , Waiman Long , Ingo Molnar , Benjamin Herrenschmidt , Alexander Viro , Jeff Layton , Miklos Szeredi , Ingo Molnar , Thomas Gleixner , linux-fsdevel , Linux Kernel Mailing List , Peter Zijlstra , Andi Kleen , "Chandramouleeswaran, Aswin" , "Norton, Scott J" Subject: Re: [PATCH v7 1/4] spinlock: A new lockref structure for lockless update of refcount Message-ID: <20130830121227.3915ffb3@gandalf.local.home> In-Reply-To: References: <1375758759-29629-1-git-send-email-Waiman.Long@hp.com> <1375758759-29629-2-git-send-email-Waiman.Long@hp.com> <1377751465.4028.20.camel@pasglop> <20130829070012.GC27322@gmail.com> <52200DAE.2020303@hp.com> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.20; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 787 Lines: 22 On Fri, 30 Aug 2013 17:38:47 +0200 Sedat Dilek wrote: > A Samsung series-5 ultrabook. > > $ grep "model name" /proc/cpuinfo | uniq > model name : Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz I believe the number of CPUs is more important. But as this is an ultrabook, I doubt that is very high. Now I know this isn't going to be popular, but I'll suggest it anyway. What about only implementing the lockref locking when CPUs are greater than 7, 7 or less will still use the normal optimized spinlocks. -- Steve -- 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/