+30
−4
Loading
There are cases for users to add a new memory region during runtime, in earlier SPDK versions before 23.01, SPDK supported this feature via restart the device for any new SET_MEM_TABLE messages. In the commit 23baa676 we removed this support to start device only once, since users are still requiring this feature, so adding it back. For SEM_MEM_TABLE vhost-user message, DPDK will hold the access lock of vring, we can't call `rte_vhost_vring_call` in the DPDK vhost thread context, so use the non-block API instead. Fix issue #3132. Signed-off-by:Changpeng Liu <changpeng.liu@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/19932 (master) (cherry picked from commit 8ef5cfc6) Change-Id: I6dcb427eb56b778d9804f89c5998b2179ea3a916 Signed-off-by:
Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20096 Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by:
Konrad Sztyber <konrad.sztyber@intel.com>