+3
−0
+18
−3
+105
−32
+31
−8
File changed.
Preview size limit exceeded, changes collapsed.
+87
−14
Loading
All of the RPCs in lib/nvmf/nvmf_rpc.c rely on knowing which nvmf_tgt they should work with. They have historically relied on the assumption that there will only be a single target in a given application. This is true for the example application in the spdk repo, but it is not necessarily true generally, By adding an option tgt_name parameter to the RPCs we enable them for multi-target NVMe-oF applications. We also further reduce the coupling between the library and the example application. Change-Id: I03b6695da05a42af3024842ed87d2ce2c296f33f Signed-off-by:Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/465442 Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by:
Ben Walker <benjamin.walker@intel.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com> Reviewed-by:
Paul Luse <paul.e.luse@intel.com>
File changed.
Preview size limit exceeded, changes collapsed.