From mboxrd@z Thu Jan 1 00:00:00 1970 From: Waiman Long Subject: Re: [PATCH v7 1/4] spinlock: A new lockref structure for lockless update of refcount Date: Thu, 29 Aug 2013 11:20:38 -0400 Message-ID: <521F66C6.6060401@hp.com> References: <1375758759-29629-1-git-send-email-Waiman.Long@hp.com> <1375758759-29629-2-git-send-email-Waiman.Long@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Viro , Jeff Layton , Miklos Szeredi , Ingo Molnar , Thomas Gleixner , linux-fsdevel , Linux Kernel Mailing List , Peter Zijlstra , Steven Rostedt , Benjamin Herrenschmidt , Andi Kleen , "Chandramouleeswaran, Aswin" , "Norton, Scott J" To: Linus Torvalds Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 08/28/2013 09:40 PM, Linus Torvalds wrote: > Just FYI: I've merged two preparatory patches in my tree for the whole > lockref thing. Instead of applying your four patches as-is during the > merge window, I ended up writing two patches that introduce the > concept and use it in the dentry code *without* introducing any of the > new semantics yet. > > Waiman, I attributed the patches to you, even if they don't actually > look much like any of the patches you sent out. And because I was > trying very hard to make sure that no actual semantics changed, my > version doesn't have the dget_parent() lockless update code, for > example. I literally just did a search-and-replace of "->d_count" with > "->d_lockref.count" and then I fixed up a few things by hand (undid > one replacement in a comment, and used the helper functions where they > were semantically identical). > > You don't have to rewrite your patches if you don't want to, I'm > planning on cherry-picking the actual code changes during the merge > window. > > Linus Thanks for merging the 2 preparatory patches for me. I will rebase my patches with the latest linux git tree. A new v8 patch set will be sent out sometime next week. I am looking forward to the v3.12 merge window which I think is coming soon. Cheer, Longman