From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [PATCH] vfs: avoid taking locks if inode not in lists Date: Thu, 28 Jul 2011 06:41:09 +0200 Message-ID: <1311828069.2697.27.camel@edumazet-laptop> References: <1311294452.2576.18.camel@schen9-DESK> <20110723132411.GA22183@infradead.org> <1311633550.2576.33.camel@schen9-DESK> <20110725225154.GD22133@ZenIV.linux.org.uk> <1311636178.2576.34.camel@schen9-DESK> <1311660013.2996.6.camel@edumazet-laptop> <1311668466.2355.12.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20110726090357.GA13013@infradead.org> <1311672994.2355.17.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <1311780065.2356.18.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20110727204415.GA13308@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Tim Chen , Al Viro , David Miller , Andi Kleen , Matthew Wilcox , Anton Blanchard , npiggin@kernel.dk, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, netdev To: Christoph Hellwig Return-path: In-Reply-To: <20110727204415.GA13308@infradead.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Le mercredi 27 juillet 2011 =C3=A0 16:44 -0400, Christoph Hellwig a =C3= =A9crit : > On Wed, Jul 27, 2011 at 05:21:05PM +0200, Eric Dumazet wrote: > > If I am not mistaken, we can add unlocked checks on the three hot s= pots. > >=20 > > After following patch, a close(socket(PF_INET, SOCK_DGRAM, 0)) pair= on > > my dev machine takes ~3us instead of ~9us. > >=20 > > Maybe its better to split it in three patches, just let me know. >=20 > I think three patches would be a lot cleaner. >=20 > As for safety of the unlocked checks: >=20 > - inode are either hashed when created or never, so that one looks > fine. > - same for the sb list. > - the writeback list is a bit more dynamic as we move things around > quite a bit. But in additon to the inode_wb_list_del call from > evict() it only ever gets remove in writeback_single_inode, which > for a freeing inode can only be called from the callers of evict()= =2E >=20 > Btw, I wonder if you should micro-optimize things a bit further by > moving the unhashed checks from the deletion functions into the calle= rs > and thus save a function call for each of them. >=20 What about following patch, addressing the micro-optimization and Andi Kleen concern about evict() readability ? Thanks ! [PATCH] vfs: avoid taking inode_hash_lock on pipes and sockets Some inodes (pipes, sockets, ...) are not hashed, no need to take contended inode_hash_lock at dismantle time. nice speedup on SMP machines on socket intensive workloads. Signed-off-by: Eric Dumazet --- fs/inode.c | 6 +++--- include/linux/fs.h | 9 ++++++++- 2 files changed, 11 insertions(+), 4 deletions(-) diff --git a/fs/inode.c b/fs/inode.c index d0c72ff..73b5598 100644 --- a/fs/inode.c +++ b/fs/inode.c @@ -399,12 +399,12 @@ void __insert_inode_hash(struct inode *inode, uns= igned long hashval) EXPORT_SYMBOL(__insert_inode_hash); =20 /** - * remove_inode_hash - remove an inode from the hash + * __remove_inode_hash - remove an inode from the hash * @inode: inode to unhash * * Remove an inode from the superblock. */ -void remove_inode_hash(struct inode *inode) +void __remove_inode_hash(struct inode *inode) { spin_lock(&inode_hash_lock); spin_lock(&inode->i_lock); @@ -412,7 +412,7 @@ void remove_inode_hash(struct inode *inode) spin_unlock(&inode->i_lock); spin_unlock(&inode_hash_lock); } -EXPORT_SYMBOL(remove_inode_hash); +EXPORT_SYMBOL(__remove_inode_hash); =20 void end_writeback(struct inode *inode) { diff --git a/include/linux/fs.h b/include/linux/fs.h index f23bcb7..786b3b1 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h @@ -2317,11 +2317,18 @@ extern int should_remove_suid(struct dentry *); extern int file_remove_suid(struct file *); =20 extern void __insert_inode_hash(struct inode *, unsigned long hashval)= ; -extern void remove_inode_hash(struct inode *); static inline void insert_inode_hash(struct inode *inode) { __insert_inode_hash(inode, inode->i_ino); } + +extern void __remove_inode_hash(struct inode *); +static inline void remove_inode_hash(struct inode *inode) +{ + if (!inode_unhashed(inode)) + __remove_inode_hash(inode); +} + extern void inode_sb_list_add(struct inode *inode); =20 #ifdef CONFIG_BLOCK -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html