Darek Stojaczyk 14a6ca08db vhost: call start/stop backend callbacks directly on the DPDK thread ... Particular backends will now be responsible for sending events to vsession->lcore. This was previously done by the generic vhost layer, but since some backends will need different lcore assignment policies soon, we need to give them more power now. Change-Id: I72cbbccb9d5a5b2358acca6d4b6bb882131937af Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/441580 Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com>		2019-01-24 17:37:03 +00:00
..
rte_vhost	vhost: do not close a closed connfd	2019-01-16 05:11:58 +00:00
Makefile	vhost_user_nvme: add vhost user nvme target to SPDK	2018-04-03 15:01:24 -04:00
vhost_blk.c	vhost: call start/stop backend callbacks directly on the DPDK thread	2019-01-24 17:37:03 +00:00
vhost_internal.h	vhost: call start/stop backend callbacks directly on the DPDK thread	2019-01-24 17:37:03 +00:00
vhost_nvme.c	vhost: call start/stop backend callbacks directly on the DPDK thread	2019-01-24 17:37:03 +00:00
vhost_rpc.c	vhost_nvme/rpc: free partially decoded request	2019-01-22 01:09:59 +00:00
vhost_scsi.c	vhost: call start/stop backend callbacks directly on the DPDK thread	2019-01-24 17:37:03 +00:00
vhost.c	vhost: call start/stop backend callbacks directly on the DPDK thread	2019-01-24 17:37:03 +00:00