| commit | 3091854e27242d09453004b011f701fa29c0b8e8 | [log] [tgz] |
|---|---|---|
| author | Keiichi Watanabe <keiichiw@chromium.org> | Fri Jul 09 08:34:48 2021 |
| committer | Keiichi Watanabe <keiichiw@chromium.org> | Fri Jul 09 08:34:48 2021 |
| tree | c4513d000e87f9f277d477026748e0a909cf1a22 | |
| parent | eaca5d36a2701c99b354ab5bc0954a78dfc9ff4f [diff] | |
| parent | 12fa07029bb4dd2293900c080d741f33b26b8698 [diff] |
Merge remote-tracking branch 'upstream/master' into HEAD Conflicts: Cargo.toml src/vhost_user/connection.rs They conflicted with "0323efc use sys_util and tempfile from crosvm". BUG=none TEST=cargo test --all-features Cq-Depend: chromium:2884021 Change-Id: I383721c587a065679078237e175f048152b8d6ec
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:
The main relationship among Traits and Structs exported by the vhost crate is as below:
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.
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.