From: Steven Pratt <slpratt@austin.ibm.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: nodatacsum broken?
Date: Mon, 16 Nov 2009 10:22:59 -0600 [thread overview]
Message-ID: <4B017C63.5000600@austin.ibm.com> (raw)
Did we break the ability to run with -o nodatacsum somewhere along the
way? I had not run just this option in a while (usually doing nodatacow
which implies nodatacsum). Just did a full run with just nodatacsum and
it looks like we still did csums.
from proc/mounts:
/dev/ffsbdev1 on /mnt/ffsb1 type btrfs (rw,nodatacsum)
but profile:
samples % app name symbol name
1664460 15.3103 vmlinux-2.6.31-autokern1 copy_user_generic_unrolled
1514349 13.9295 vmlinux-2.6.31-autokern1 crc32c
606147 5.5756 vmlinux-2.6.31-autokern1 rb_get_reader_page
562936 5.1781 vmlinux-2.6.31-autokern1 mutex_spin_on_owner
433405 3.9866 vmlinux-2.6.31-autokern1 ring_buffer_consume
This was for a sequential read test on the unstable tree from 11-12.
Steve
next reply other threads:[~2009-11-16 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 16:22 Steven Pratt [this message]
2009-11-16 16:27 ` nodatacsum broken? Chris Mason
2009-11-16 16:51 ` Steven Pratt
2009-11-16 17:23 ` Chris Mason
2009-11-16 17:40 ` Steven Pratt
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=4B017C63.5000600@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=linux-btrfs@vger.kernel.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