From e0ee5887f7c7b0dae9783405947f0f03de3d3353 Mon Sep 17 00:00:00 2001 From: Liu Jiang Date: Wed, 3 Apr 2019 14:38:29 +0800 Subject: Initial commit --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 README.md (limited to 'README.md') diff --git a/README.md b/README.md new file mode 100644 index 0000000..6426bd6 --- /dev/null +++ b/README.md @@ -0,0 +1,10 @@ +# vHost +A crate to implement the vHost ioctl interfaces and vHost-user protocol. + +## vHost Ioctl Interfaces +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 Protocol +The vHost-user protocol is aiming to complement 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. -- cgit v1.2.3