Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / third_party / rust-vmm / vhost / refs/heads/stabilize-13851.B
commit6ae7e17c9ac65410e20c12d628539c4fc06cf16b[log] [tgz]
authorKeiichi Watanabe <keiichiw@chromium.org>Wed Feb 24 21:40:38 2021 +0900
committerCommit Bot <commit-bot@chromium.org>Fri Mar 12 03:21:51 2021 +0000
treed319b91a928880b8454341fdfe22e850210c63e7
parentbb69fe9808ed6047393e55296699440474b05c25 [diff]
Add PRESUBMIT.cfg for clippy

BUG=b:181227406
TEST=run `repo upload`

Change-Id: I8f599f979758f2d0fb99fdc2e1c47c84bb49d48e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/rust-vmm/vhost/+/2717907
Tested-by: Keiichi Watanabe <keiichiw@chromium.org>
Auto-Submit: Keiichi Watanabe <keiichiw@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Commit-Queue: Chirantan Ekbote <chirantan@chromium.org>
1 file changed
tree: d319b91a928880b8454341fdfe22e850210c63e7
  1. .cargo/
  2. docs/
  3. src/
  4. rust-vmm-ci
  5. .gitignore
  6. .gitmodules
  7. Cargo.toml
  8. CODEOWNERS
  9. coverage_config_aarch64.json
  10. coverage_config_x86_64.json
  11. LICENSE
  12. LICENSE-BSD-3-Clause
  13. LICENSE-BSD-Chromium
  14. OWNERS
  15. PRESUBMIT.cfg
  16. README.md
README.md

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.