be78c6da49
The unit tests are run from cargo test through multiple threads of the same process. For this reason, all these threads share their file descriptors (because that's how this works on Linux), which means that any of them can close a file descriptor opened from another thread. In the context of create_listener() and accept_connection() tests, they can run concurrently and this generates some failure when the file descriptor create_listener() is binding to is being closed from the accept_connection() test. In order to avoid such race condition, this patch simply removes the part of the unit test performing an explicit and unsafe file descriptor closure. Fixes #759 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| LICENSE | ||
| LICENSE-BSD | ||
| LICENSE-MIT | ||
| README.md | ||
vHost
A crate to support vhost backend drivers for virtio devices.
Kernel-based vHost Backend Drivers
The vhost drivers in Linux provide in-kernel virtio device emulation. Normally the hypervisor userspace process emulates I/O accesses from the guest. Vhost puts virtio emulation code into the kernel, taking hypervisor userspace out of the picture. This allows device emulation code to directly call into kernel subsystems instead of performing system calls from userspace. The hypervisor relies on ioctl based interfaces to control those in-kernel vhost drivers, such as vhost-net, vhost-scsi and vhost-vsock etc.
vHost-user Backend Drivers
The vhost-user protocol is aiming to implement vhost backend drivers in userspace, which complements the ioctl interface used to control the vhost implementation in the Linux kernel. It implements the control plane needed to establish virtqueue sharing with a user space process on the same host. It uses communication over a Unix domain socket to share file descriptors in the ancillary data of the message.
The protocol defines two sides of the communication, master and slave. Master is the application that shares its virtqueues, slave is the consumer of the virtqueues. Master and slave can be either a client (i.e. connecting) or server (listening) in the socket communication.