+1
−1
+1
−1
Loading
These changes were added since last release, so it's safe to just change them now without breaking API/ABI. I mistakenly used uint32_t for the socket_id, when in fact DPDK and our env layer really treat it as an int. This mostly shows up with the SPDK_ENV_SOCKET_ID_ANY that is defined as -1, which forces a lot of annoying casting if we're trying to pass this value through a uint32_t interface. This socket_id concept will be getting plumbed into nvme, bdev and nvmf layers, so instead of proliferating the uint32_t socket_id there, just change sock layer to use int32_t instead. Signed-off-by:Jim Harris <jim.harris@samsung.com> Change-Id: I573ba7f9aeed3b216bef72f39fc671c9c6688d3a Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/24577 Reviewed-by:
Ben Walker <ben@nvidia.com> Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-by:
Aleksey Marchuk <alexeymar@nvidia.com>