From: Dave Chinner <david@fromorbit.com>
To: viro@ZenIV.linux.org.uk
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: vfs: inode lock breakup
Date: Tue, 22 Mar 2011 22:23:35 +1100 [thread overview]
Message-ID: <1300793023-3775-1-git-send-email-david@fromorbit.com> (raw)
Hi Al,
The following patches are the inode_lock breakup series originally
derived from Nick Piggin's vfs-scale tree. I've kind of been sitting
on them until the dcache_lock breakup and rcu path-walk has had some
time to be shaken out. The patch ѕet is pretty much unchanged from
the last round of review last last year - all I've done to bring it
up to date is forward port it and run it through some testing on XFS
and ext4.
I know it's late in the .39 merge window, but I hope you'll consider
it if the patches are still acceptable(*). Otherwise I'm happy to take
the time to get it right for .40.
Cheers,
Dave.
(*) The series can also be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev.git inode-scale
Dave Chinner (8):
fs: protect inode->i_state with inode->i_lock
fs: factor inode disposal
fs: Lock the inode LRU list separately
fs: remove inode_lock from iput_final and prune_icache
fs: move i_sb_list out from under inode_lock
fs: move i_wb_list out from under inode_lock
fs: rename inode_lock to inode_hash_lock
fs: pull inode->i_lock up out of writeback_single_inode
Documentation/filesystems/Locking | 2 +-
Documentation/filesystems/porting | 16 +-
Documentation/filesystems/vfs.txt | 2 +-
fs/block_dev.c | 6 +-
fs/buffer.c | 2 +-
fs/drop_caches.c | 18 +-
fs/fs-writeback.c | 141 ++++++++-----
fs/inode.c | 416 +++++++++++++++++++++----------------
fs/internal.h | 7 +
fs/logfs/inode.c | 2 +-
fs/notify/inode_mark.c | 42 +++--
fs/notify/mark.c | 1 -
fs/notify/vfsmount_mark.c | 1 -
fs/ntfs/inode.c | 4 +-
fs/quota/dquot.c | 41 ++--
include/linux/fs.h | 2 +-
include/linux/quotaops.h | 2 +-
include/linux/writeback.h | 2 +-
mm/backing-dev.c | 8 +-
mm/filemap.c | 10 +-
mm/rmap.c | 5 +-
21 files changed, 434 insertions(+), 296 deletions(-)
next reply other threads:[~2011-03-22 11:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 11:23 Dave Chinner [this message]
2011-03-22 11:23 ` [PATCH 1/8] fs: protect inode->i_state with inode->i_lock Dave Chinner
2011-03-22 11:23 ` [PATCH 2/8] fs: factor inode disposal Dave Chinner
2011-03-22 11:23 ` [PATCH 3/8] fs: Lock the inode LRU list separately Dave Chinner
2011-03-22 11:23 ` [PATCH 4/8] fs: remove inode_lock from iput_final and prune_icache Dave Chinner
2011-03-22 11:23 ` [PATCH 5/8] fs: move i_sb_list out from under inode_lock Dave Chinner
2011-03-22 11:23 ` [PATCH 6/8] fs: move i_wb_list " Dave Chinner
2011-03-22 11:23 ` [PATCH 7/8] fs: rename inode_lock to inode_hash_lock Dave Chinner
2011-03-22 11:23 ` [PATCH 8/8] fs: pull inode->i_lock up out of writeback_single_inode Dave Chinner
2011-03-22 18:17 ` vfs: inode lock breakup Sedat Dilek
2011-03-23 6:29 ` Dave Chinner
2011-03-23 7:53 ` Sedat Dilek
2011-03-23 23:36 ` Dave Chinner
2011-03-23 19:03 ` [PATCH 9/8] fs: simplify iget & friends Christoph Hellwig
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=1300793023-3775-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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