From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: akpm@osdl.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove sb->s_files and file_list_lock usage in dquot.c
Date: Tue, 6 Feb 2007 14:46:29 +0100 [thread overview]
Message-ID: <20070206134629.GG328@duck.suse.cz> (raw)
In-Reply-To: <20070206132333.GA9919@lst.de>
On Tue 06-02-07 14:23:33, Christoph Hellwig wrote:
> Iterate over sb->s_inodes instead of sb->s_files in add_dquot_ref.
> This reduces list search and lock hold time aswell as getting rid of
> one of the few uses of file_list_lock which Ingo identified as a
> scalability problem.
>
> Previously we called dq_op->initialize for every inode handing of
> a writeable file that wasn't initialized before. Now we're calling
> it for every inode that has a non-zero i_writecount, aka a writeable
> file descriptor refering to it.
>
> Thanks a lot to Jan Kara for running this patch through his quota
> test harness.
>
> Note: this is ontop of '[PATCH] move remove_dquot_ref to dqout.c'
> which I sent out yesterday.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jan Kara <jack@suse.cz>
> Index: linux-2.6/fs/dquot.c
> ===================================================================
> --- linux-2.6.orig/fs/dquot.c 2007-02-05 18:54:36.000000000 +0100
> +++ linux-2.6/fs/dquot.c 2007-02-05 18:59:48.000000000 +0100
> @@ -689,23 +689,27 @@
> /* This routine is guarded by dqonoff_mutex mutex */
> static void add_dquot_ref(struct super_block *sb, int type)
> {
> - struct list_head *p;
> + struct inode *inode;
>
> restart:
> - file_list_lock();
> - list_for_each(p, &sb->s_files) {
> - struct file *filp = list_entry(p, struct file, f_u.fu_list);
> - struct inode *inode = filp->f_path.dentry->d_inode;
> - if (filp->f_mode & FMODE_WRITE && dqinit_needed(inode, type)) {
> - struct dentry *dentry = dget(filp->f_path.dentry);
> - file_list_unlock();
> - sb->dq_op->initialize(inode, type);
> - dput(dentry);
> - /* As we may have blocked we had better restart... */
> - goto restart;
> - }
> + spin_lock(&inode_lock);
> + list_for_each_entry(inode, &sb->s_inodes, i_sb_list) {
> + if (!atomic_read(&inode->i_writecount))
> + continue;
> + if (!dqinit_needed(inode, type))
> + continue;
> + if (inode->i_state & (I_FREEING|I_WILL_FREE))
> + continue;
> +
> + __iget(inode);
> + spin_unlock(&inode_lock);
> +
> + sb->dq_op->initialize(inode, type);
> + iput(inode);
> + /* As we may have blocked we had better restart... */
> + goto restart;
> }
> - file_list_unlock();
> + spin_unlock(&inode_lock);
> }
>
> /* Return 0 if dqput() won't block (note that 1 doesn't necessarily mean blocking) */
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next prev parent reply other threads:[~2007-02-06 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 13:23 [PATCH] remove sb->s_files and file_list_lock usage in dquot.c Christoph Hellwig
2007-02-06 13:46 ` Jan Kara [this message]
2007-02-06 23:50 ` Andrew Morton
2007-02-07 7:22 ` Christoph Hellwig
2007-02-07 18:03 ` Jan Engelhardt
2007-02-07 19:06 ` Christoph Hellwig
2007-02-08 12:22 ` Jan Engelhardt
2007-02-07 8:35 ` Jan Kara
2007-02-08 9:01 ` Bill Huey
2007-02-09 7:14 ` Bill Huey
2007-02-09 7:23 ` Bill Huey
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=20070206134629.GG328@duck.suse.cz \
--to=jack@suse.cz \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).