From: Ben Myers <bpm@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Debunking myths about metadata CRC overhead
Date: Tue, 4 Jun 2013 11:20:30 -0500 [thread overview]
Message-ID: <20130604162030.GJ20932@sgi.com> (raw)
In-Reply-To: <20130604025307.GB29466@dastard>
Dave,
On Tue, Jun 04, 2013 at 12:53:07PM +1000, Dave Chinner wrote:
> On Mon, Jun 03, 2013 at 11:10:11AM +0200, Emmanuel Florac wrote:
> > Le Mon, 3 Jun 2013 17:44:52 +1000 vous écriviez:
> >
> > > There has been some assertions made recently that metadata CRCs have
> > > too much overhead to always be enabled. So I'll run some quick
> > > benchmarks to demonstrate the "too much overhead" assertions are
> > > completely unfounded.
> >
> > Just a quick question: what is the minimal kernel version and xfsprogs
> > version needed to run xfs with metadata CRC? I'd happily test it on
> > real hardware, I have a couple of storage servers in test in the 40 to
> > 108 TB range.
>
> If the maintainers merge all the patches I send for the 3.10-rc
> series, then the 3.10 release should be stable enough to use for
> testing with data you don't care if you lose.
>
> As for the userspace code - that is still just a patchset. I haven't
> had any feedback from the maintainers about it in the past month, so
> I've got no idea what they are doing with it. I'll post out a new
> version in the next couple of days - it's 50-odd patches by now, so
> it'd be nice to have it in the xfsprogs git tree so people could
> just pull it and build it for testing purposes by the time that 3.10
> releases....
When it is reviewed and adequately tested we'll pull it in. Until then
Emmanuel will need to pull down the patchset. Right now the focus is on
3.10.
-Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-04 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 7:44 Debunking myths about metadata CRC overhead Dave Chinner
2013-06-03 9:10 ` Emmanuel Florac
2013-06-04 2:53 ` Dave Chinner
2013-06-04 16:20 ` Ben Myers [this message]
2013-06-04 22:06 ` Dave Chinner
2013-06-04 22:09 ` Ben Myers
2013-06-04 18:38 ` Chandra Seetharaman
2013-06-04 22:08 ` Dave Chinner
2013-06-04 22:40 ` Chandra Seetharaman
2013-06-04 22:59 ` Dave Chinner
2013-06-03 15:31 ` Troy McCorkell
2013-06-03 20:00 ` Geoffrey Wehrman
2013-06-04 2:43 ` Dave Chinner
2013-06-04 10:19 ` Dave Chinner
2013-06-04 21:27 ` Geoffrey Wehrman
2013-06-05 0:27 ` 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=20130604162030.GJ20932@sgi.com \
--to=bpm@sgi.com \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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