2f10d28007
The driver still may use batches to implement some operations or for efficiency reasons. Batching my be resurrected in the future, but for now we need to do some fairly extensive performance changes on the driver and eliminating all of this unused/inactive code makes that much easier. Change-Id: I92fcec9e4c7424771f053123d821cc57dba9793c Signed-off-by: Ben Walker <benjamin.walker@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/10348 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com>
994 B
994 B
IDXD Driver
Public Interface
- spdk/idxd.h
Key Functions
| Function | Description |
|---|---|
| spdk_idxd_probe() | @copybrief spdk_idxd_probe() |
| spdk_idxd_submit_copy() | @copybrief spdk_idxd_submit_copy() |
| spdk_idxd_submit_compare() | @copybrief spdk_idxd_submit_compare() |
| spdk_idxd_submit_crc32c() | @copybrief spdk_idxd_submit_crc32c() |
| spdk_idxd_submit_dualcast | @copybrief spdk_idxd_submit_dualcast() |
| spdk_idxd_submit_fill() | @copybrief spdk_idxd_submit_fill() |
Pre-defined configurations
The RPC idxd_scan_accel_engine is used to both enable IDXD and set it's
configuration to one of two pre-defined configs:
Config #0: 4 groups, 1 work queue per group, 1 engine per group. Config #1: 2 groups, 2 work queues per group, 2 engines per group.