What problem does it solve?
Teams with existing OpenSSL-based pipelines want to accelerate SHA hashing on NVIDIA BlueField DPUs or ConnectX NICs without rewriting their applications against the doca-sha C API, and they need a reliable way to prove the hardware offload actually engaged instead of silently falling back to software SHA.
Core Features & Use Cases
- Engine Load Mechanics: Guides loading the DOCA SHA Offload Engine via
openssl engine dynamic or the programmatic ENGINE_load_dynamic / ENGINE_by_id / ENGINE_ctrl_cmd_string sequence, including PCIe address selection with the set_pci_addr ctrl-cmd.
- Offload Verification: Teaches the SHA-224 negative test and the
-engine_impl flag that prove the engine actually computed the digest rather than OpenSSL falling back to software SHA.
- Performance Characterization: Walks through
openssl speed comparisons with -async_jobs and -multi to find the message-size window where offload beats CPU SHA on the user's actual hardware.
- Use Case: An operator running
openssl dgst -sha256 in a production pipeline on a BlueField host uses this Skill to load the engine, verify offload with the SHA-224 negative test, and benchmark whether their message-size mix benefits before committing to deployment.
Quick Start
Ask your agent to help you load the DOCA SHA Offload Engine into your existing OpenSSL pipeline and verify that SHA-256 digests are actually offloaded to the hardware.