doca-sha

Create a doca_sha context on a doca_dev, enable the hash task with doca_sha_task_hash_set_conf before doca_ctx_start, set source and destination mmap permissions, then submit tasks and drive completions via doca_pe_progress. Query doca_sha_cap_* first to confirm the device supports your algorithm.

Use one-shot doca_sha_task_hash when the input fits in a single source buffer within max_src_buf_size. Use partial hash when the input exceeds that limit or arrives in chunks; never mark a partial task final before submitting at least one intermediate chunk, as that is undefined behavior.

Skip doca-sha for tiny one-shot hashes, since DMA setup cost exceeds CPU time, and when the device does not support your algorithm — use OpenSSL instead. Offload pays off for bulk inputs of a few hundred KiB or more, repeated hashing, or data already pinned in doca_mmap memory.

This error means the destination buffer is smaller than doca_sha_cap_get_min_dst_buf_size for the chosen algorithm, or the source buffer exceeds doca_sha_cap_get_max_src_buf_size. Re-run the capability queries against the active doca_devinfo and resize the buffers accordingly.

The public enum surface covers only DOCA_SHA_ALGORITHM_SHA1, SHA256, and SHA512 — no MD5, SHA-3, or Blake. Always confirm support at runtime with doca_sha_cap_task_hash_get_supported against the active device rather than assuming from documentation.

A submitted task with no completion event almost always means the progress engine is not being driven. Add doca_pe_progress calls in your main loop so completion events are drained from the queue.