On 12/04/2013 10:54 AM, Nikos Mavrogiannopoulos wrote:
On Wed, 2013-12-04 at 10:20 +0100, Karl Hiramoto wrote:
I think the issue might be the memory alignment, the HW wants 16 byte
alignment.
I do echo 9 > /proc/sys/ioctl/cryptodev_verbosity
and start to see messages liks:
[ 1102.870000] cryptodev: openvpn[693] (get_userbuf:157): careful -
destination address 267d3f is not 16 byte aligned
[ 1103.880000] cryptodev: openvpn[693] (get_userbuf:152): careful -
source address 2665fb is not 16 byte aligned
[ 1103.890000] cryptodev: openvpn[693] (get_userbuf:157): careful -
destination address 267d3f is not 16 byte aligned
[ 1104.700000] cryptodev: openvpn[693] (get_userbuf:152): careful -
source address 266dbb is not 16 byte aligned
[ 1104.890000] cryptodev: openvpn[693] (get_userbuf:152): careful -
source address 2665fb is not 16 byte aligned
Could you then try modifying main.c, at crypto_run() to set the
COP_FLAG_NO_ZC if there is no 16-byte alignment? If that fixes the
issue, we should see how we can handle it depending on the driver.
Yes, it does fix it. However performance is really bad, it's about 5%
slower than doing the crypto in software.
So the only way to still use the zero-copy would be to fix openvpn?
Thanks
Karl
_______________________________________________
Cryptodev-linux-devel mailing list
Cryptodev-linux-devel@gna.org
https://mail.gna.org/listinfo/cryptodev-linux-devel
