vmsilo fork of vhost rust libraries
Find a file
Stefano Garzarella 1215bae8a9 Remove parse_iotlb_msg from VhostIotlbBackend
This function is not used and possible users can call directly
`parse` on structures implementing VhostIotlbMsgParser trait.

Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
2021-10-19 11:55:37 +08:00
.buildkite Deprecate custom pipeline 2021-09-03 10:16:46 +03:00
.cargo fix link issues on aarch64 musl 2020-09-04 17:59:53 +03:00
.github update dependabot formatting 2021-09-10 13:49:37 +03:00
docs Prepare for publishing to crates.io 2021-03-01 12:50:56 +01:00
rust-vmm-ci@7931077cdc build(deps): bump rust-vmm-ci from 7f22582 to 7931077 2021-10-12 09:44:14 +03:00
src Remove parse_iotlb_msg from VhostIotlbBackend 2021-10-19 11:55:37 +08:00
.gitignore Update .gitignore file 2021-03-01 12:50:56 +01:00
.gitmodules Switch to rust-vmm-ci for the CI 2020-09-04 17:59:53 +03:00
Cargo.toml Cargo: replace wildcard with 0.5 for serial_test 2021-09-23 08:57:05 +02:00
CHANGELOG.md Prepare for release v0.2.0 2021-09-23 06:50:11 +02:00
CODEOWNERS CODEOWNERS: add stefano-garzarella 2021-08-31 16:48:22 +08:00
coverage_config_aarch64.json Switch to rust-vmm-ci for the CI 2020-09-04 17:59:53 +03:00
coverage_config_x86_64.json Add VhostVdpa trait 2021-09-15 15:01:53 +08:00
LICENSE Initial commit 2019-04-03 14:38:29 +08:00
LICENSE-BSD-Google Prepare for release v0.1 2021-08-05 17:51:35 +02:00
README.md Prepare for publishing to crates.io 2021-03-01 12:50:56 +01:00

vHost

A pure rust library for vDPA, vhost and vhost-user.

The vhost crate aims to help implementing dataplane for virtio backend drivers. It supports three different types of dataplane drivers:

  • vhost: the dataplane is implemented by linux kernel
  • vhost-user: the dataplane is implemented by dedicated vhost-user servers
  • vDPA(vhost DataPath Accelerator): the dataplane is implemented by hardwares

The main relationship among Traits and Structs exported by the vhost crate is as below:

vhost Architecture

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 aims 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.