From: austin zhang <austin_zhang@linux.intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>, johnpol@2ka.mipt.ru
Cc: 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: Thu, 10 Jul 2008 07:26:09 -0400 [thread overview]
Message-ID: <1215689169.5257.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20080709074153.GA11927@gondor.apana.org.au>
On Wed, 2008-07-09 at 15:41 +0800, Herbert Xu wrote:
> I've just converted the crc32c module over to the new interface.
> You can use this as an example.
Herbert and Evgeniy,
Sorry for late reply. Thanks a lot for your information and example, I
will work out the intel-specific implemetation. After internal
discussing and approval, I will post here for review again.
> Unfortunately this leads to nasty hacks because the existing
> interface does chaining in a way that isn't easily mapped over
> to the crypto API. However this is no great loss since there
> is a grand total of two users in the tree :)
>
> So my plan is to convert them and then remove the libcrc32c
> interface completely.
Because libcrc32c can be a module in original implemetation, so for
those other routine which call crc32c_le directly, this may not work for
them?
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-10 11:27 UTC|newest]
Thread overview: 5+ 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 12:00 ` Evgeniy Polyakov
2008-07-09 7:41 ` Herbert Xu
2008-07-10 11:26 ` austin zhang [this message]
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=1215689169.5257.7.camel@localhost.localdomain \
--to=austin_zhang@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=chaapala@cisco.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=johnpol@2ka.mipt.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox