Hi.
On Tue, Jul 08, 2008 at 06:25:54AM -0400, austin zhang ([EMAIL PROTECTED])
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
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
