All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fb.com>
To: <linux-fsdevel@vger.kernel.org>, <kernel-team@fb.com>,
	<viro@ZenIV.linux.org.uk>, <hch@infradead.org>,
	<david@fromorbit.com>, <jack@suse.cz>
Subject: [PATCH 0/8] super block scalability patches V4
Date: Tue, 23 Jun 2015 20:23:54 -0700	[thread overview]
Message-ID: <1435116242-27495-1-git-send-email-jbacik@fb.com> (raw)

This is the latest round of patches, it includes all the new reviewed-by's, the
fixed up 'bdi: add a new writeback list for sync' patch that has Jan's
suggestions included and Dave's patch folded in to address the problem he saw in
testing.  I've rebased these on Linus's master from this evening.  Al would you
please consider pulling


git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git superblock-scaling

Thanks,

Josef

             reply	other threads:[~2015-06-24  3:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  3:23 Josef Bacik [this message]
2015-06-24  3:23 ` [PATCH 1/8] writeback: plug writeback at a high level Josef Bacik
2015-06-24  3:23 ` [PATCH 2/8] inode: add hlist_fake to avoid the inode hash lock in evict Josef Bacik
2015-06-24  3:23 ` [PATCH 3/8] inode: convert inode_sb_list_lock to per-sb Josef Bacik
2015-06-24  3:23 ` [PATCH 4/8] sync: serialise per-superblock sync operations Josef Bacik
2015-06-24  3:23 ` [PATCH 5/8] inode: rename i_wb_list to i_io_list Josef Bacik
2015-06-24  3:24 ` [PATCH 6/8] bdi: add a new writeback list for sync Josef Bacik
2015-12-09 18:40   ` Brian Foster
2015-12-10 10:08     ` Jan Kara
2015-12-11 14:37       ` Brian Foster
2015-06-24  3:24 ` [PATCH 7/8] writeback: periodically trim the writeback list Josef Bacik
2015-06-24  3:24 ` [PATCH 8/8] inode: don't softlockup when evicting inodes 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=1435116242-27495-1-git-send-email-jbacik@fb.com \
    --to=jbacik@fb.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.