svn commit: r345040 - in stable/11: share/man/man4 sys/conf sys/dev/cxgbe sys/dev/cxgbe/crypto sys/dev/cxgbe/firmware sys/modules/cxgbe sys/modules/cxgbe/ccr sys/powerpc/conf

[John Baldwin]

On 3/12/19 6:32 AM, Slawa Olhovchenkov wrote:
> On Mon, Mar 11, 2019 at 11:16:10PM +0000, John Baldwin wrote:
> 
>> Author: jhb
>> Date: Mon Mar 11 23:16:10 2019
>> New Revision: 345040
>> URL: https://svnweb.freebsd.org/changeset/base/345040
>>
>> Log:
>>   MFC 318429,318967,319721,319723,323600,323724,328353-328361,330042,343056:
>>   Add a driver for the Chelsio T6 crypto accelerator engine.
> 
> Where I can find example/manual of use this engine from userspace?

It's hard to use usefully from userspace (even in 12/head).  I have some
old patches for openssl 1.0.2's cryptodev engine to teach it about more
of the algorithms supported by OCF including the TLS variant of AES-GCM,
but I found that the overhead of the extra copies made it not very
compelling compared to using AES-NI in userland.  (I had some extra
changes to make /dev/crypto wire the user pages to avoid the copies
and that got the /dev/crypto case down to break-even with doing AES-NI
in userland.)  In the kernel I see better performance where using T6
to offload crypto for IPsec does use less CPU at higher throughput than
using CPU instructions though for AES-GCM AES-NI on the CPU is pretty
close.

-- 
John Baldwin