From: Matt Mackall <mpm@selenic.com>
To: Clay Haapala <chaapala@cisco.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Add CRC32C chksums to crypto routines
Date: Thu, 15 Jan 2004 19:40:37 -0600 [thread overview]
Message-ID: <20040116014037.GN28521@waste.org> (raw)
In-Reply-To: <yqujisje43q9.fsf@chaapala-lnx2.cisco.com>
On Wed, Jan 14, 2004 at 03:31:10PM -0600, Clay Haapala wrote:
> This patch against 2.6.1 adds CRC32C checksumming capabilities to the
> crypto routines. The structure of it is based wholly on the existing
> digest (md5) routines, the main difference being that chksums are
> often used in an "accumulator" fashion, effectively requiring one to
> set the seed, and the digest algorithms don't do that.
>
> CRC32C is a 32-bit CRC variant used by the iSCSI protocol and in other
> drivers. iSCSI uses scatterlists, so it was strongly suggested by the
> SCSI maintainers during reviews of Version 4 of the linux-iscsi driver
> that the code be added to the crypto routines, which operate on
> scatterlists.
>
> Test routines have been added to tcrypt.c.
>
> The linux-iscsi project can be found on SourceForge:
> http://sourceforge.net/projects/linux-iscsi/
Clay!
The cryptoapi stuff seems sensible, but we've already got at least one
copy of the core crc32c code in the kernel at net/sctp/crc32c.c. It'd
be better to work with the sctp folks to push this into lib/crc32.c.
Handling multiple polynomials shouldn't be too painful there.
--
Matt Mackall : http://www.selenic.com : Linux development and consulting
next prev parent reply other threads:[~2004-01-16 1:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 21:31 [PATCH] Add CRC32C chksums to crypto routines Clay Haapala
2004-01-14 21:45 ` James Morris
2004-01-14 22:12 ` Clay Haapala
2004-01-16 1:40 ` Matt Mackall [this message]
2004-01-19 20:13 ` James Morris
2004-01-19 21:15 ` Clay Haapala
2004-01-19 21:33 ` James Morris
2004-02-03 16:58 ` [PATCH 2.6.1] Add CRC32C chksums to crypto and lib routines Clay Haapala
2004-02-03 17:09 ` James Morris
2004-02-04 17:07 ` Clay Haapala
2004-02-03 17:13 ` James Morris
2004-02-03 17:50 ` [PATCH 2.6.1 -- take two] " Clay Haapala
2004-02-03 18:51 ` Matt Mackall
2004-02-03 19:13 ` Clay Haapala
2004-02-03 19:27 ` Matt Mackall
2004-02-03 20:17 ` James Morris
2004-02-03 23:25 ` Matt Domsch
2004-02-03 23:37 ` Matt Mackall
2004-02-04 16:14 ` Clay Haapala
2004-02-04 17:21 ` Matt Mackall
2004-02-07 15:20 ` Matt Domsch
2004-02-18 21:24 ` Matt Domsch
2004-02-18 23:18 ` Matt Domsch
2004-02-06 23:54 ` Jamie Lokier
2004-02-04 2:18 ` James Morris
2004-02-04 3:11 ` Valdis.Kletnieks
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=20040116014037.GN28521@waste.org \
--to=mpm@selenic.com \
--cc=chaapala@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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