public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Austin Zhang <austin_zhang@linux.intel.com>
To: Pavel Machek <pavel@suse.cz>
Cc: herbert@gondor.apana.org.au, bunk@kernel.org,
	dwmw2@infradead.org, davem@davemloft.net,
	randy.dunlap@oracle.com, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
Date: Wed, 06 Aug 2008 07:05:27 -0400	[thread overview]
Message-ID: <1218020727.29030.16.camel@localhost.localdomain> (raw)
In-Reply-To: <20080806094226.GA23685@atrey.karlin.mff.cuni.cz>

Paval,

Thanks for your comments. 

On Wed, 2008-08-06 at 11:42 +0200, Pavel Machek wrote:
> Copyright / GPL?
Yes, as : +MODULE_LICENSE("GPL");

> > +#ifdef CONFIG_X86_64
> > +#define REX_PRE "0x48, "
> > +#define SCALE_F 8
> > +#else
> > +#define REX_PRE
> > +#define SCALE_F 4
> > +#endif
> 
> Ouch...
Any good suggestion will be appreciated. 

> > +static u32 crc32c_intel_le_hw_byte(u32 crc, unsigned char const *data, size_t length)
> > +{
> > +	while (length--) {
> > +		__asm__ __volatile__(
> 
> Are all the underscores neccessary?
What's big impact if keep those underscores? Just keep ANSI C  style.


> 
> > +		return -1;
> 
> That's supposed to be errno, right?
Are you suggest "ENODEV"? It's a feature from the device but the device is exact here. 
And for the crc32c algorithm, there would be possible that several
algorithms registered themselves in crypto and user will don't care
which implementation will server him even the hardware accelerated
implementation don't exist in this processor. 





  parent reply	other threads:[~2008-08-06 11:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06  5:23 [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3 Austin Zhang
2008-08-06  9:42 ` Pavel Machek
2008-08-06 11:03   ` Herbert Xu
2008-08-06 11:05   ` Austin Zhang [this message]
2008-08-06 11:17     ` Herbert Xu
2008-08-06 11:20       ` Austin Zhang
2008-08-06 11:22       ` Herbert Xu
2008-08-06 12:14     ` Pavel Machek
2008-08-07  2:00       ` Herbert Xu
2008-08-06 10:09 ` Herbert Xu
2008-08-08  3:38 ` Ulrich Drepper
2008-08-08 13:35   ` Herbert Xu
2008-08-11 16:10     ` Pavel Machek
2008-08-13  1:14       ` 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=1218020727.29030.16.camel@localhost.localdomain \
    --to=austin_zhang@linux.intel.com \
    --cc=bunk@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=randy.dunlap@oracle.com \
    /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