From: Herbert Xu <herbert@gondor.hengli.com.au>
To: Bob Pearson <rpearson@systemfabricworks.com>
Cc: djwong@us.ibm.com, adilger.kernel@dilger.ca, tytso@mit.edu,
davem@davemloft.net, linux-kernel@vger.kernel.org,
cmm@us.ibm.com, linux-crypto@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/3] crc32c: Implement a self-test for CRC32c
Date: Thu, 1 Sep 2011 11:51:21 +1000 [thread overview]
Message-ID: <20110901015120.GA26182@gondor.apana.org.au> (raw)
In-Reply-To: <035501cc6845$66a0ad20$33e20760$@systemfabricworks.com>
Bob Pearson <rpearson@systemfabricworks.com> wrote:
> Could you elaborate a little on this?
Sure, we already have a self-test infrastructure under crypto
in testmgr.*. It even includes test vectors for crc32c.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2011-09-01 1:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 0:33 [PATCH v1 0/3] crc32c: Add faster algorithm and self-test code Darrick J. Wong
2011-09-01 0:33 ` [PATCH 1/3] crc32c: Implement CRC32c with slicing-by-8 algorithm Darrick J. Wong
2011-09-01 0:33 ` [PATCH 2/3] libcrc32c: Expose big-endian version of crc32c Darrick J. Wong
2011-09-01 0:33 ` [PATCH 3/3] crc32c: Implement a self-test for CRC32c Darrick J. Wong
2011-09-01 1:07 ` Herbert Xu
2011-09-01 1:20 ` Bob Pearson
2011-09-01 1:51 ` Herbert Xu [this message]
2011-09-01 5:40 ` Bob Pearson
2011-09-01 6:41 ` Herbert Xu
2011-09-01 22:18 ` Darrick J. Wong
2011-09-01 22:24 ` Christoph Hellwig
2011-09-01 22:28 ` Darrick J. Wong
2011-09-27 22:12 [PATCH v2 0/3] crc32c: Add faster algorithm and self-test code Darrick J. Wong
2011-09-27 22:13 ` [PATCH 3/3] crc32c: Implement a self-test for CRC32c Darrick J. Wong
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=20110901015120.GA26182@gondor.apana.org.au \
--to=herbert@gondor.hengli.com.au \
--cc=adilger.kernel@dilger.ca \
--cc=cmm@us.ibm.com \
--cc=davem@davemloft.net \
--cc=djwong@us.ibm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpearson@systemfabricworks.com \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®