From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] mkfs: default to CRC enabled filesystems
Date: Fri, 20 Mar 2015 11:38:46 -0700 [thread overview]
Message-ID: <20150320183846.GH24608@birch.djwong.org> (raw)
In-Reply-To: <550B858D.4030003@tlinx.org>
On Thu, Mar 19, 2015 at 07:27:25PM -0700, Linda Walsh wrote:
> Dave Chinner wrote:
> >From: Dave Chinner <dchinner@redhat.com>
> >
> >It's time to change the mkfs defaults to enable CRCs for all new
> >filesystems.
> ---
> "Sounds good", but what exactly is CRC'ed?
>
> I.e. all data? Or how much data/second would I expect
> to 'need' CRC'ing?
>
> Some quick timing stuff:
>
> >time dd if=/dev/zero of=1G bs=1M count=1024 oflag=direct
> 1024+0 records in
> 1024+0 records out
> 1073741824 bytes (1.1 GB) copied, 1.76947 s, 607 MB/s
> 1.77sec 0.00usr 0.50sys (28.38% cpu)
>
> >dropcaches
> 76.34sec 0.00usr 69.22sys (90.69% cpu)
>
> Ishtar:law/bin> time crc32 1G ## no cache
> 5B64C2B0
> 6.67sec 3.85usr 0.94sys (71.82% cpu)
>
> >time crc32 1G ## in cache
> 5B64C2B0
> 4.00sec 3.57usr 0.42sys (100.00% cpu)
> (using Xeon X5660 @ 2.80GHz)
Usually the kernel will load one of the CRC32c accelerators to reduce the
impact of the metadata checksumming. Not sure if 'crc32' knows how to use
the new instructions Intel built into that X5660, though I'm guessing not.
Also, XFS uses crc32c, not crc32.
--D
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-03-20 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 23:22 [PATCH] mkfs: default to CRC enabled filesystems Dave Chinner
2015-03-19 14:55 ` Eric Sandeen
2015-03-19 14:58 ` Eric Sandeen
2015-03-19 23:13 ` Dave Chinner
2015-03-20 15:26 ` Eric Sandeen
2015-03-20 21:47 ` Dave Chinner
2015-03-20 21:56 ` Eric Sandeen
2015-03-20 2:27 ` Linda Walsh
2015-03-20 2:44 ` Greg Freemyer
2015-03-20 18:38 ` Darrick J. Wong [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=20150320183846.GH24608@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/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