From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: austin zhang <austin_zhang@linux.intel.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
chaapala@cisco.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, arjan@linux.intel.com
Subject: Re: FW: [Fwd: [PATCH]Using Intel CRC32 instruction to implement hardware accelerated CRC32c algorithm.]
Date: Tue, 8 Jul 2008 16:00:53 +0400 [thread overview]
Message-ID: <20080708120050.GA6410@2ka.mipt.ru> (raw)
In-Reply-To: <1215512754.2906.23.camel@localhost.localdomain>
Hi.
On Tue, Jul 08, 2008 at 06:25:54AM -0400, austin zhang (austin_zhang@linux.intel.com) wrote:
> > designed to support sync just as well as async despite the name)
> Do you mean use async_xxx interface?
No, async_xxx is very different hardware assist, although it can be
converted to cryptoapi too.
> > to rewrite the crypto/crc32c implementation such that one tfm can
> > be used by multiple users. All that has to be done is to move
> > the state from the tfm into the request object.
>
> > 2) Convert all crc32c users to use the crypto interface and phase
> > out lib/crc32c completely.
> >
> > 3) Add the Intel-specific crc32c implementation through the crypto
> > API.
> Agreed. And which module in crypto is the template for following the crypto API?
This is some kind of how cbc(cipher) or ecb(cipher) templates are done:
cbc(aes), cbc(aes-i686) for example.
The same would be possible to do with crc32c but for checksumming (which
is effectively a hash).
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-07-08 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000901c8e0d4$6f5cf230$7fb410ac@ccr.corp.intel.com>
2008-07-08 10:25 ` FW: [Fwd: [PATCH]Using Intel CRC32 instruction to implement hardware accelerated CRC32c algorithm.] austin zhang
2008-07-08 10:25 ` austin zhang
2008-07-08 12:00 ` Evgeniy Polyakov [this message]
2008-07-09 7:41 ` Herbert Xu
2008-07-10 11:26 ` austin zhang
2008-07-10 11:26 ` austin zhang
2008-07-10 12:52 ` Herbert Xu
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=20080708120050.GA6410@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=arjan@linux.intel.com \
--cc=austin_zhang@linux.intel.com \
--cc=chaapala@cisco.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.