From: Christoph Hellwig <hch@infradead.org>
To: Josef Bacik <jbacik@fb.com>
Cc: linux-fsdevel@vger.kernel.org, kernel-team@fb.com,
viro@ZenIV.linux.org.uk, hch@infradead.org, jack@suse.cz,
david@fromorbit.com, Dave Chinner <dchinner@redhat.com>
Subject: Re: [PATCH 3/8] inode: convert inode_sb_list_lock to per-sb
Date: Wed, 17 Jun 2015 05:06:10 -0700 [thread overview]
Message-ID: <20150617120610.GC20286@infradead.org> (raw)
In-Reply-To: <1434051673-13838-4-git-send-email-jbacik@fb.com>
On Thu, Jun 11, 2015 at 03:41:08PM -0400, Josef Bacik wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> The process of reducing contention on per-superblock inode lists
> starts with moving the locking to match the per-superblock inode
> list. This takes the global lock out of the picture and reduces the
> contention problems to within a single filesystem. This doesn't get
> rid of contention as the locks still have global CPU scope, but it
> does isolate operations on different superblocks form each other.
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2015-06-17 12:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 19:41 [PATCH 0/7] super block scalabilit patches V3 Josef Bacik
2015-06-11 19:41 ` [PATCH 1/8] writeback: plug writeback at a high level Josef Bacik
2015-06-17 12:03 ` Christoph Hellwig
2015-06-11 19:41 ` [PATCH 2/8] inode: add hlist_fake to avoid the inode hash lock in evict Josef Bacik
2015-06-17 12:03 ` Christoph Hellwig
2015-06-11 19:41 ` [PATCH 3/8] inode: convert inode_sb_list_lock to per-sb Josef Bacik
2015-06-17 12:06 ` Christoph Hellwig [this message]
2015-06-11 19:41 ` [PATCH 4/8] sync: serialise per-superblock sync operations Josef Bacik
2015-06-17 12:06 ` Christoph Hellwig
2015-06-11 19:41 ` [PATCH 5/8] inode: rename i_wb_list to i_io_list Josef Bacik
2015-06-17 12:06 ` Christoph Hellwig
2015-06-11 19:41 ` [PATCH 6/8] bdi: add a new writeback list for sync Josef Bacik
2015-06-15 14:12 ` Jan Kara
2015-06-16 15:42 ` Josef Bacik
2015-06-17 10:34 ` Jan Kara
2015-06-17 17:55 ` Josef Bacik
2015-06-18 9:28 ` Jan Kara
2015-06-18 22:18 ` [PATCH 6/8 V4] " Josef Bacik
2015-06-19 8:38 ` Jan Kara
2015-06-11 19:41 ` [PATCH 7/8] writeback: periodically trim the writeback list Josef Bacik
2015-06-11 19:41 ` [PATCH 8/8] inode: don't softlockup when evicting inodes Josef Bacik
2015-06-15 14:16 ` Jan Kara
2015-06-11 20:50 ` [PATCH 0/7] super block scalabilit patches V3 Tejun Heo
2015-06-15 21:34 ` Dave Chinner
2015-06-22 2:26 ` [PATCH] sync: wait_sb_inodes() calls iput() with spinlock held (was Re: [PATCH 0/7] super block scalabilit patches V3) Dave Chinner
2015-06-22 16:21 ` Josef Bacik
2015-06-23 23:14 ` Josef Bacik
2015-06-24 0:35 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2015-06-24 3:23 [PATCH 0/8] super block scalability patches V4 Josef Bacik
2015-06-24 3:23 ` [PATCH 3/8] inode: convert inode_sb_list_lock to per-sb Josef Bacik
2015-03-20 17:14 [PATCH 0/8] Sync and VFS scalability improvements V2 Josef Bacik
2015-03-20 17:14 ` [PATCH 3/8] inode: convert inode_sb_list_lock to per-sb Josef Bacik
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=20150617120610.GC20286@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=jack@suse.cz \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).