Re: [Ocf-linux-users] ocf-linux and newer kernels/hardware drivers

[David M. <Dav...@se...>]

Jivin Mark Gillespie lays it down ...
> Hi, I have a marvel kirkwood based Sheevaplug, and kernel 2.6.32 brings a
> new crypto hardware driver "mv_cesa".   I have patched my kernel with the
> latest ocf-linux patch over kernel 2.6.32, and it applied cleanly, aside
> from a few line offsets, the kernel boots, and I have a /dev/crypto.
> I have compiled cryptotest and it runs, but does not seem to to use the
> mv_cesa driver.

The mv_cesa driver in 2.6.32 is a kernel cryptoapi driver and not an OCF
driver.  AFAIK is currently only supports AES and not all the
ciphers/hashses and AEAD interfaces that you may want.  Currently I think
it's primary purpose is dm-crypt.

In order for OCF to use that driver you will need to use the OCF cryptosoft
driver,  and it will need to be modified to handle the ASYNC Crypto-API
interface as well as the sync interface it currently uses.

The other option is to use the OCF native driver that Marvell wrote.  It
performs well.  You will need to turn off the mv_cesa driver if you do that
though,  they will not be compatible.  Not sure where you get this exactly,
but I think it comes with their 2.6.22 kernel.

> Does the ocf-linux patch need to be aware of the driver?   Are there any
> updated patches that include this?  Is it easy to hack it myself?

We have 2.6.32 running on a Marvell 88f6281 here and are working on the
changes needed,  but they could be a few weeks out yet based on silly
season time lines and holidays :-)

It's not completely trivial and is made somewhat harder by the sparse doc
for the cryptoapi in the kernel.

> PS.  There is a discussion about this here:  http://plugcomputer.org/plugforum/index.php?topic=1014.msg6588#msg6588 

Feel free to pass on any info you want to share with the group,

Cheers,
Davidm

-- 
David McCullough,  dav...@se...,  Ph:+61 734352815
McAfee - SnapGear  http://www.snapgear.com                http://www.uCdot.org