From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sedat Dilek Subject: Re: [PATCH v7 1/4] spinlock: A new lockref structure for lockless update of refcount Date: Fri, 30 Aug 2013 18:16:22 +0200 Message-ID: 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> <20130830121227.3915ffb3@gandalf.local.home> Reply-To: sedat.dilek@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 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" To: Steven Rostedt Return-path: In-Reply-To: <20130830121227.3915ffb3@gandalf.local.home> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, Aug 30, 2013 at 6:12 PM, Steven Rostedt wrote: > 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. > Fantastic Four. > 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. > I have seen that spinlock-lockref stuff is more important on that monster-machines. It's good to see it does not break "smaller" systems. - Sedat -