f3edd7a359
The nvme cuse IOCTLs are actually creating passthru commands that can be either IO passthru commands or admin commands. Renaming the routines to correctly reflect that should limit the confusion when reading the code. Passthru commands that are admin commands will go to the spdk_nvme_ctrlr_cmd_admin_raw interface and passthru commands that are IO will be sent to the spdk_nvme_ctrlr_cmd_io_raw interface. Signed-off-by: Curt Bruns <curt.e.bruns@gmail.com> Change-Id: I8d427fe8b5f503fdb2d193236c77d410d5b13886 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/7740 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| cuse.c | ||
| Makefile | ||
| nvme_cuse_rpc.sh | ||
| nvme_cuse.sh | ||
| nvme_ns_manage_cuse.sh | ||
| spdk_nvme_cli_cuse.sh | ||
| spdk_smartctl_cuse.sh | ||