From: Troy McCorkell <tdm@sgi.com>
To: xfs@oss.sgi.com
Subject: Re: Debunking myths about metadata CRC overhead
Date: Mon, 03 Jun 2013 10:31:17 -0500 [thread overview]
Message-ID: <51ACB6C5.8010400@sgi.com> (raw)
In-Reply-To: <20130603074452.GZ29466@dastard>
On 06/03/2013 02:44 AM, Dave Chinner wrote:
> Hi folks,
>
> 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.
>
>
>
Dave,
Thanks for generating, gathering, and providing this data.
Thanks,
Troy
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-03 15:31 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
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 [this message]
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=51ACB6C5.8010400@sgi.com \
--to=tdm@sgi.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 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.