From: Dave Chinner <david@fromorbit.com>
To: Nick Piggin <npiggin@gmail.com>
Cc: Dave Chinner <dchinner@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Status of inode scaling work
Date: Tue, 25 Jan 2011 18:10:11 +1100 [thread overview]
Message-ID: <20110125071011.GD28803@dastard> (raw)
In-Reply-To: <AANLkTinpZ2Qf1W2qocGhMNki_7b9G1xt=83b5QvwJXxb@mail.gmail.com>
On Fri, Jan 14, 2011 at 08:02:57PM +1100, Nick Piggin wrote:
> I'd like to know about the status and plans of the inode scaling work.
>
> Aiming for 2.6.39 or 40 might be an idea.
It was ready for 2.6.38....
> I'd like to be able to see what patches are proposed to finish breaking
> inode_lock into its constituent sub classes, and we can go from there.
Already done. I pointed you at the tree a while back:
The following changes since commit c723fdab8aa728dc2bf0da6a0de8bb9c3f588d84:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/sfrench/cifs-2.6 (2011-01-25 14:23:54 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/xfsdev.git inode-scale
Dave Chinner (9):
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: Clean up documentation references to inode_lock
fs: pull inode->i_lock up out of writeback_single_inode
Documentation/filesystems/Locking | 2 +-
Documentation/filesystems/porting | 11 +-
Documentation/filesystems/vfs.txt | 2 +-
fs/block_dev.c | 4 +-
fs/buffer.c | 2 +-
fs/drop_caches.c | 18 +-
fs/fs-writeback.c | 138 ++++++++-----
fs/inode.c | 395 +++++++++++++++++++++----------------
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 | 7 +-
21 files changed, 409 insertions(+), 292 deletions(-)
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2011-01-25 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 9:02 Status of inode scaling work Nick Piggin
2011-01-25 7:10 ` Dave Chinner [this message]
2011-01-27 0:40 ` Nick Piggin
2011-01-27 4:57 ` Dave Chinner
2011-01-27 5:11 ` Nick Piggin
2011-01-27 6:20 ` Dave Chinner
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=20110125071011.GD28803@dastard \
--to=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).