From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guo Chao Subject: [RFC v4 Patch 0/4] fs/inode.c: optimization for inode lock usage Date: Fri, 21 Sep 2012 17:31:02 +0800 Message-ID: <1348219866-1799-1-git-send-email-yan@linux.vnet.ibm.com> Cc: dchinner@redhat.com, hch@infradead.org, jack@suse.cz, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: viro@zeniv.linux.org.uk Return-path: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org This patchset optimizes several places which take the per inode spin lock. They have not been fully tested yet, thus they are marked as RFC. I do limited tests after all patches applied: use two 'find' to traverse the filesystems and touch all files in parallel. This runs for several days in a virtual machine, no suspicious log appears. Guo Chao (4): fs/inode.c: do not take i_lock on newly allocated inode fs/inode.c: do not take i_lock in __(insert|remove)_inode_hash fs/inode.c: do not take i_lock when identify an inode fs/inode.c: always take i_lock before calling filesystem's test() method fs/inode.c | 32 +++++++++----------------------- 1 file changed, 9 insertions(+), 23 deletions(-) -- 1.7.9.5