From: Clay Haapala <chaapala@cisco.com>
To: James Morris <jmorris@redhat.com>
Cc: linux-kernel@vger.kernel.org, <linux-scsi@vger.kernel.org>,
"David S. Miller" <davem@redhat.com>
Subject: Re: [PATCH] Add CRC32C chksums to crypto routines
Date: Wed, 14 Jan 2004 16:12:31 -0600 [thread overview]
Message-ID: <yqujzncq2n8w.fsf@chaapala-lnx2.cisco.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0401141643560.12649-100000@thoron.boston.redhat.com> (James Morris's message of "Wed, 14 Jan 2004 16:45:49 -0500 (EST)")
On Wed, 14 Jan 2004, James Morris stated:
> On Wed, 14 Jan 2004, 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.
>
> This looks interesting; do you know of any other chksum algorithms
> which might need to be implemented in the kernel?
>
I reference the one other user of CRC32C in my code, that would be the
sctp network driver, at this time.
Of course, there is library/crc32, which I did make an attempt to
implement companion code to it, but we really need the "work over
scatterlists" feature of the crypto routines.
I took the design goals the of the library/crc32 routines (flexible
XOR policy, flexible initial values) and tried to allow that in the
crypto chksum routines. CRC32 could be moved into it, but the uses of
CRC32 are often quick accumulation over packet fragments, rather than
computing digests over scatterlists describing would can be many K of
data.
--
Clay Haapala (chaapala@cisco.com) Cisco Systems SRBU +1 763-398-1056
6450 Wedgwood Rd, Suite 130 Maple Grove MN 55311 PGP: C89240AD
Funny, I didn't think Haliburton was into aerospace.
next prev parent reply other threads:[~2004-01-14 22:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 21:31 Clay Haapala
2004-01-14 21:45 ` James Morris
2004-01-14 22:12 ` Clay Haapala [this message]
2004-01-16 1:40 ` Matt Mackall
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=yqujzncq2n8w.fsf@chaapala-lnx2.cisco.com \
--to=chaapala@cisco.com \
--cc=davem@redhat.com \
--cc=jmorris@redhat.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
all inboxes | Powered by JetHome®