From: "Bill O'Donnell" <billodo@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@sgi.com
Subject: Re: [PATCH 0/9] CRC support for superblock, ag headers, log and btree blocks
Date: Mon, 1 Dec 2008 17:53:18 -0600 [thread overview]
Message-ID: <20081201235318.GC5094@sgi.com> (raw)
In-Reply-To: <20080925225613.GA9822@lst.de>
On Fri, Sep 26, 2008 at 12:56:13AM +0200, Christoph Hellwig wrote:
| Here's an updated crc series for various metadata structures. We're still
| looking at the magic number in the log recovery case because getting down
| a buffer type for the other structures wasn't quite as easy as for the
| btree block. I'll probably look into that again once we're done with all
| data structures.
I've carried out cursory build and test of this series. I'm concerned that
my testing (and anyone else's testing) has not addressed performance hits
being introduced with crc on metadata. What level of testing have you done,
and can you recommend some testing that goes beyond the QA suite that we
have in place. I did run the btree test harness on that earlier series, but it
appeared to me that that was a go/no-go test and unless I'm missing something,
I've not seen tests that might help quantify performance hits.
Thanks,
Bill
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2008-12-01 23:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 22:56 [PATCH 0/9] CRC support for superblock, ag headers, log and btree blocks Christoph Hellwig
2008-09-25 23:50 ` Dave Chinner
2008-09-26 11:10 ` Christoph Hellwig
2008-12-01 23:10 ` Bill O'Donnell
[not found] ` <20081203104409.GA15485@infradead.org>
2008-12-04 0:19 ` Bill O'Donnell
2008-12-01 23:22 ` Bill O'Donnell
2008-12-01 23:39 ` Bill O'Donnell
2008-12-01 23:53 ` Bill O'Donnell [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=20081201235318.GC5094@sgi.com \
--to=billodo@sgi.com \
--cc=hch@lst.de \
--cc=xfs@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