Re: [WIP/RFC] crypto: add support for Orion5X crypto engine

2009-03-18 Thread Sebastian Andrzej Siewior
* Evgeniy Polyakov | 2009-03-18 01:42:43 [+0300]: >Hi. Hi Evgeniy, >On Tue, Mar 17, 2009 at 10:58:44PM +0100, Sebastian Andrzej Siewior >(arm-ker...@ml.breakpoint.cc) wrote: >> +struct crypto_priv { > >Please use less generic names over the file. will do. >> +void __iomem *reg; >> +void

Re: [WIP/RFC] crypto: add support for Orion5X crypto engine

2009-03-18 Thread Martin Michlmayr
* Paulius Zaleckas [2009-03-18 17:55]: > > +config CRYPTO_DEV_MARVELL_CRYPTO_ENGINE > > CRYPTO_DEV...CRYPTO_ENGINE > Maybe CRYPTO_DEV_MARVELL would be enough? ... and since we're talking about naming issues, I think you should replace "mav" with "mv" to be in line with other uses inside the kern

Re: [WIP/RFC] crypto: add support for Orion5X crypto engine

2009-03-18 Thread Paulius Zaleckas
Sebastian Andrzej Siewior wrote: > This is version two of the the driver. New things: > - aes-ecb passes selftests > - aes-cbc passes selftests > > The driver still does memcpy() from/to sram. To solve this, a dma driver > would be required but first I wanted to compare the performance between > n

Accelerate GCM with PCLMULQDQ-NI

2009-03-18 Thread Huang Ying
Hi, In addition to AES-NI, Intel will provide PCLMULQDQ-NI (carry-less multiplication) in future CPU to accelerate GCM mode. The document can be found here: http://software.intel.com/en-us/articles/carry-less-multiplication-and-its-usage-for-computing-the-gcm-mode/ It follows the same design as