linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Josef Bacik <jbacik@fb.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	dchinner@redhat.com, kernel-team@fb.com
Subject: Re: [GIT PULL] superblock scalability patches
Date: Sat, 22 Aug 2015 08:45:28 +1000	[thread overview]
Message-ID: <20150821224528.GY714@dastard> (raw)
In-Reply-To: <55D4C276.2040806@fb.com>

On Wed, Aug 19, 2015 at 10:52:54AM -0700, Josef Bacik wrote:
> Hello,
> 
> Al would you please consider pulling from
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git
> superblock-scaling
> 
> I've rebased them onto Linus's master as of a few days ago and
> retested them to make sure they were still good to go.  They've all
> been through a lengthy review process and thoroughly tested.  The
> only change since the last time I posted the patch series is I've
> dropped the patch that created a new writeback list for sync to
> process because of the new writeback changes.  Porting that patch
> over is going to take some extra work and I don't want to hold up
> the rest of these patches any longer. Thanks,

Been testing this for a day now, it seems to be fine. The patch that
is missingis the really important scalability fix (i.e. the one that
avoids the entire inode cache walk to find dirty inodes), but I can
live with that being delayed to get all the prep merged sooner.

Tested-by: Dave Chinner <dchinner@redhat.com>

Thanks, Josef!

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2015-08-21 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 17:52 [GIT PULL] superblock scalability patches Josef Bacik
2015-08-21 22:45 ` Dave Chinner [this message]

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=20150821224528.GY714@dastard \
    --to=david@fromorbit.com \
    --cc=dchinner@redhat.com \
    --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).