vhost-nvme: reserve a bigger enough opcode to avoid conflict with QEMU

Currently QEMU vhost-nvme driver hasn't been pushed to QEMU community,
for vhost-user socket messages, QEMU can pick the opcode at any time,
QEMU 2.12 already picked 27-30 for other driver, for the purpose to
mitigate rebase work in future, while here, we reserve a bigger value
so that it will not conflict with QEMU for very long time.

Change-Id: Ic404bb14330c4acc484aa9c86983030803a31e77
Signed-off-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-on: https://review.gerrithub.io/408771
Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
Reviewed-by: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com>
Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
This commit is contained in:
Changpeng Liu 2018-04-12 00:22:04 -04:00 committed by Daniel Verkamp
parent b7060cb21a
commit c2b66a83bc

View File

@ -86,11 +86,11 @@ typedef enum VhostUserRequest {
VHOST_USER_NET_SET_MTU = 20,
VHOST_USER_GET_CONFIG = 24,
VHOST_USER_SET_CONFIG = 25,
VHOST_USER_NVME_ADMIN = 27,
VHOST_USER_NVME_SET_CQ_CALL = 28,
VHOST_USER_NVME_GET_CAP = 29,
VHOST_USER_NVME_START_STOP = 30,
VHOST_USER_NVME_IO_CMD = 31,
VHOST_USER_NVME_ADMIN = 80,
VHOST_USER_NVME_SET_CQ_CALL = 81,
VHOST_USER_NVME_GET_CAP = 82,
VHOST_USER_NVME_START_STOP = 83,
VHOST_USER_NVME_IO_CMD = 84,
VHOST_USER_MAX
} VhostUserRequest;