Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Tim Chen <tim.c.chen@linux.intel.com>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	David Miller <davem@davemloft.net>,
	Andi Kleen <andi@firstfloor.org>, Matthew Wilcox <matthew@wil.cx>,
	Anton Blanchard <anton@samba.org>,
	npiggin@kernel.dk, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: [PATCH] vfs: avoid call to inode_lru_list_del() if possible
Date: Thu, 28 Jul 2011 06:55:13 +0200	[thread overview]
Message-ID: <1311828913.2697.33.camel@edumazet-laptop> (raw)
In-Reply-To: <20110727204415.GA13308@infradead.org>

Le mercredi 27 juillet 2011 à 16:44 -0400, Christoph Hellwig a écrit :
> 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 spots.
> > 
> > After following patch, a close(socket(PF_INET, SOCK_DGRAM, 0)) pair on
> > my dev machine takes ~3us instead of ~9us.
> > 
> > Maybe its better to split it in three patches, just let me know.
> 
> I think three patches would be a lot cleaner.
> 
> As for safety of the unlocked checks:
> 
>  - 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().
> 
> Btw, I wonder if you should micro-optimize things a bit further by
> moving the unhashed checks from the deletion functions into the callers
> and thus save a function call for each of them.
> 

Here is the last patch, addressing inode_lru_list_del() call.

Only the call done from iput_final() can obviously benefit from checking
i_lru being empty or not, so it makes sense to perform the check at
caller site instead of doing it in inode_lru_list_del()

[PATCH] vfs: avoid call to inode_lru_list_del() if possible

inode_lru_list_del() is expensive because of per superblock lru locking,
while some inodes are not in lru list.

Adding a check in iput_final() can speedup pipe/sockets workloads on
SMP.

Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
 fs/inode.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/fs/inode.c b/fs/inode.c
index d0c72ff..b8b8939 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -1328,7 +1328,8 @@ static void iput_final(struct inode *inode)
 	}
 
 	inode->i_state |= I_FREEING;
-	inode_lru_list_del(inode);
+	if (!list_empty(&inode->i_lru))
+		inode_lru_list_del(inode);
 	spin_unlock(&inode->i_lock);
 
 	evict(inode);


--
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

      parent reply	other threads:[~2011-07-28  4:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110717010427.GC5359@parisc-linux.org>
     [not found] ` <20110717084630.GC8006@one.firstfloor.org>
     [not found]   ` <1310977028.5756.1.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
     [not found]     ` <20110718154008.GA29593@infradead.org>
     [not found]       ` <20110718155141.GA11013@ZenIV.linux.org.uk>
     [not found]         ` <1311093158.2707.75.camel@schen9-DESK>
     [not found]           ` <20110721204042.GB31405@ZenIV.linux.org.uk>
     [not found]             ` <1311294452.2576.18.camel@schen9-DESK>
     [not found]               ` <20110723132411.GA22183@infradead.org>
     [not found]                 ` <1311633550.2576.33.camel@schen9-DESK>
     [not found]                   ` <20110725225154.GD22133@ZenIV.linux.org.uk>
     [not found]                     ` <1311636178.2576.34.camel@schen9-DESK>
     [not found]                       ` <1311660013.2996.6.camel@edumazet-laptop>
2011-07-26  8:21                         ` [PATCH] vfs: dont chain pipe/anon/socket on superblock s_inodes list Eric Dumazet
2011-07-26  9:03                           ` Christoph Hellwig
2011-07-26  9:36                             ` Eric Dumazet
2011-07-26  9:42                               ` Christoph Hellwig
2011-07-26 10:43                                 ` Eric Dumazet
2011-07-26 11:49                                   ` Christoph Hellwig
2011-07-27 15:21                               ` [PATCH] vfs: avoid taking locks if inode not in lists Eric Dumazet
2011-07-27 17:12                                 ` Andi Kleen
2011-07-27 20:44                                 ` Christoph Hellwig
2011-07-27 20:59                                   ` Andi Kleen
2011-07-27 21:01                                     ` Christoph Hellwig
2011-07-28  4:11                                       ` [PATCH] vfs: conditionally call inode_wb_list_del() Eric Dumazet
2011-07-28  4:41                                   ` [PATCH] vfs: avoid taking locks if inode not in lists Eric Dumazet
2011-07-28  4:55                                   ` Eric Dumazet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1311828913.2697.33.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=anton@samba.org \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=netdev@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    --cc=tim.c.chen@linux.intel.com \
    --cc=viro@ZenIV.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox