On Fri, Dec 02, 2011 at 06:30:37PM -0800, Darrick J. Wong wrote:
> On Fri, Dec 02, 2011 at 08:23:58AM +0800, Herbert Xu wrote:
> > On Thu, Dec 01, 2011 at 12:31:22PM -0800, Darrick J. Wong wrote:
> > .
> > > They seem to call crc32c(), which is in crypto/crc32c. If you're
> > > interested in
> >
On Fri, Dec 02, 2011 at 08:23:58AM +0800, Herbert Xu wrote:
> On Thu, Dec 01, 2011 at 12:31:22PM -0800, Darrick J. Wong wrote:
> .
> > They seem to call crc32c(), which is in crypto/crc32c. If you're
> > interested in
>
> Nope, the crypto API layer will use the SSE implementation
> where availab
On Thu, Dec 01, 2011 at 12:31:22PM -0800, Darrick J. Wong wrote:
.
> They seem to call crc32c(), which is in crypto/crc32c. If you're interested
> in
Nope, the crypto API layer will use the SSE implementation
where available. Only when it isn't available will the C version
in crypto/ be used.
On Thu, Dec 01, 2011 at 12:20:53PM -0800, Joel Becker wrote:
> On Thu, Dec 01, 2011 at 12:13:41PM -0800, Darrick J. Wong wrote:
> > Hi all,
> >
> > This patchset (re)uses Bob Pearson's crc32 slice-by-8 code to stamp out a
> > software crc32c implementation. It removes the crc32c implementation in
On Thu, Dec 01, 2011 at 12:13:41PM -0800, Darrick J. Wong wrote:
> Hi all,
>
> This patchset (re)uses Bob Pearson's crc32 slice-by-8 code to stamp out a
> software crc32c implementation. It removes the crc32c implementation in
> crypto/ in favor of using the stamped-out one in lib/. There is als
