d58a2f6cc5
We enable multiple engines by: * getting rid of the globals that point to the one available HW and one available SW engine * adding a submit_tasks() entry point for the SW engine so that it is treated like any other engine allowing us to just call submit_tasks() to the assigned engine for the opcode instead of checking what is supported * changing the definition of engine capabilities from "HW accelerated" to simply "supported" * during init, use a global (g_engines_opc) that contains engines and is indexed by opcode so we know what the best engine is for each op code * future patches will add RPC's to override engine priorities or specifically assign an opcode(s) to an engine. Signed-off-by: paul luse <paul.e.luse@intel.com> Change-Id: I9b9f3d5a2e499124aa7ccf71f0da83c8ee3dd9f9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/11870 Community-CI: Mellanox Build Bot Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com> |
||
|---|---|---|
| .. | ||
| idxd | ||
| ioat | ||
| Makefile | ||