Date: Thu, 9 Jan 2020 16:53:26 +0100 From: Patryk Duda <pdk@semihalf.com> To: freebsd-arch@freebsd.org Subject: Re: CFT: Open Crypto Framework Changes: Round 1 Message-ID: <CAGOBvLoaemMSE3_purDPxRYNRd80V4gChNaxXLpqm9eCRhyfRw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi John, I tested ocf_rework branch on device which has cesa support. Output from "cryptocheck -vz -a all" doesn't differ when kernel was compiled from ocf_rework and from e0f7c88b6c (commit before changes). In both cases I can get the same number of interrupts generated by cesa using "vmstat -i". Nevertheless when I'm running IPSec (Strongswan acts as IKE daemon) software crypto is used instead of cesa. Performance is poor and no cesa interrupts are generated. When running kernel built from commit e0f7c88b6c IPSec works fine. Strongswan is configured to use only AES128 CBC + SHA256 HMAC. This combination is supported by cesa, confirmed by cryptocheck. In my opinion something between IPSec and cesa is broken. Best regards, Patryk PS This message was sent twice because for the first time I was not subscribed for mailing list and my message got stuck in moderation.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGOBvLoaemMSE3_purDPxRYNRd80V4gChNaxXLpqm9eCRhyfRw>