8b0a4a3c53
Virtqueues now have to be "acquired" by a logical CPU core in order to perform any traffic on them. The acquire mechanism is thread-safe to prevent two reactors accessing the same virtqueue at the same time. For now a single virtqueue may be used by only one io_channel. Support for shared virtqueues will be implemented in future. Added new param "Queues" to the virtio config file for VirtioUser bdevs. VirtioPci will use the max available queues num - negotiated during QEMU startup. Change-Id: I3fd4b9d8c470f26ca9b84838b3c64de6f9e48300 Signed-off-by: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/377337 Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> |
||
---|---|---|
.. | ||
bdev | ||
blob | ||
blobfs | ||
conf | ||
copy | ||
cunit | ||
env_dpdk | ||
event | ||
ioat | ||
iscsi | ||
json | ||
jsonrpc | ||
log | ||
lvol | ||
nbd | ||
net | ||
nvme | ||
nvmf | ||
rocksdb | ||
rpc | ||
scsi | ||
trace | ||
ut_mock | ||
util | ||
vhost | ||
Makefile |