Page MenuHomeFreeBSD

Add qat(4)
ClosedPublic

Authored by markj on Oct 26 2020, 7:50 PM.
Tags
None
Referenced Files
F80137645: D26963.id78790.diff
Thu, Mar 28, 10:48 AM
Unknown Object (File)
Fri, Mar 22, 4:21 PM
Unknown Object (File)
Jan 13 2024, 11:37 AM
Unknown Object (File)
Dec 20 2023, 3:06 AM
Unknown Object (File)
Dec 3 2023, 7:34 PM
Unknown Object (File)
Dec 3 2023, 7:34 PM
Unknown Object (File)
Dec 3 2023, 7:34 PM
Unknown Object (File)
Dec 3 2023, 7:34 PM

Details

Reviewers
gnn
jhb
Group Reviewers
manpages
Commits
rS367386: Add qat(4)
Summary

This diff provides an Intel QAT driver and opencrypto interface
implementation. The driver was ported from NetBSD, which in turn seems
partially based on the (BSD-licensed) Linux QAT driver. I made a number
of changes:

  • modifications to support the new opencrypto interface in head
  • support for GMAC/AES-GCM, AES-CTR and AES-XTS
  • support for detaching the driver
  • various bug fixes
  • DH895X support

A couple of things are not implemented yet but are in progress:

  • separate input and output buffers (done separately to simplify an initial merge to stable/12)

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

markj requested review of this revision.Oct 26 2020, 7:50 PM
markj created this revision.

Do you know if it is possible to do SHA512/256 (SHA512 truncated to 256 bits, but it uses a different initial state)?

Do you know if it is possible to do SHA512/256 (SHA512 truncated to 256 bits, but it uses a different initial state)?

I think it should be possible. For plain SHA transforms the initial state is passed in the content descriptor, and the driver can handle the truncation. Does opencrypto have a way to request SHA512/256?

OCF does not currently have algorithms for SHA 512/256 or SHA 512/224. It does support SHA 224 (which is SHA 256/224) and SHA 384 (which is SHA 512/384). Adding support for additional algorithms is fairly straightforward. You would need to add constants and simple software versions (as we always want a fallback so kernel consumers can depend on an algorithm existing) and ideally tests in cryptocheck. Ideally there would be at least one in-kernel consumer for an algorithm though. I think the use case for SHA 512/256 is ZFS?

Lots of fixes and cleanups, especially for C2XXX hardware.

This revision was not accepted when it landed; it landed in state Needs Review.Nov 5 2020, 3:55 PM
Closed by commit rS367386: Add qat(4) (authored by markj). · Explain Why
This revision was automatically updated to reflect the committed changes.
markj added a commit: rS367386: Add qat(4).