e6a8401a1d
If a driver is registered and selected, it'll now be used to execute sequences of accel operations. The driver has priority over accel modules, so the modules will only be used to execute operations that the driver cannot perform. Once driver completes a task (or a number of tasks), it notifies accel using standard spdk_accel_task_complete(). To let accel continue processing a sequence, driver can call spdk_accel_sequence_continue(). This can be done when the driver executes all tasks (1), an error occurs (2), or the driver doesn't know how to execute a given opcode (3). In case of (3), that operation will be executed using appropriate accel module and, while the rest of the sequence will be sent back to the driver. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: If414c02073ffc731454e03d25c7ee02bef58463b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16548 Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> |
||
|---|---|---|
| .. | ||
| accel_internal.h | ||
| accel_rpc.c | ||
| accel_sw.c | ||
| accel.c | ||
| Makefile | ||
| spdk_accel.map | ||