nfv_hypervisors-kvm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
nfv_hypervisors-kvm [2015/06/29 00:07] Jun Nakajima [Scope] |
nfv_hypervisors-kvm [2015/06/30 18:03] (current) Prakash Ramchandran [Committers and Contributors] |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * Proposed name for the repository: ''kvmfornfv'' | * Proposed name for the repository: ''kvmfornfv'' | ||
| * Project Categories: | * Project Categories: | ||
| - | * Requirements | ||
| * Collaborative Development | * Collaborative Development | ||
| Line 84: | Line 83: | ||
| Data plane VNFs typically would need to use the option 1, as pointed above. The DPDK IVSHMEM library in DPDK, for example, uses shared memory (called “ivshmem”) across the VMs (See http://dpdk.org/doc/guides/prog_guide/ivshmem_lib.html). This is one of the optimal implementations available in KVM, but the ivshmem feature is not necessarily well received or maintained by the KVM/QEMU community. In addition, “security implications need to be carefully evaluated” as pointed out there. | Data plane VNFs typically would need to use the option 1, as pointed above. The DPDK IVSHMEM library in DPDK, for example, uses shared memory (called “ivshmem”) across the VMs (See http://dpdk.org/doc/guides/prog_guide/ivshmem_lib.html). This is one of the optimal implementations available in KVM, but the ivshmem feature is not necessarily well received or maintained by the KVM/QEMU community. In addition, “security implications need to be carefully evaluated” as pointed out there. | ||
| - | For the option 2, it is possible for the VMs, vSwitch, or the KVM hypervisor to lower overhead and latency using software (e.g. shared memory) or hardware virtualization features. Some of the techniques developed for such purposes are useful for the option 1 as well. For example, the virtio Poll Mode Driver (PMD) (http://dpdk.org/doc/guides/nics/virtio.html) and the vhost library (such as vhost-user) in DPDK can be helpful when providing fast inter-VM communication and VM-host communication. In addition, hardware virtualization features, such as VMFUNC could be helpful when providing protected inter-VM communication by mitigating security issues with ivshmem (See the KVM Forum 2014 pdf below for details). | + | For the option 2, it is possible for the VMs, vSwitch, or the KVM hypervisor to lower overhead and latency using software (e.g. shared memory) or hardware virtualization features. Some of the techniques developed for such purposes are useful for the option 1 as well. For example, the virtio Poll Mode Driver (PMD) (http://dpdk.org/doc/guides/nics/virtio.html) and the vhost library (such as vhost-user) in DPDK can be helpful when providing fast inter-VM communication and VM-host communication. In addition, hardware virtualization features, such as VMFUNC could be helpful when protecting inter-VM communication by mitigating security issues with ivshmem (See the KVM Forum 2014 pdf below for details). |
| For this feature, therefore, we need to take the following steps: | For this feature, therefore, we need to take the following steps: | ||
| Line 155: | Line 154: | ||
| * Manish Jaggi: Manish.Jaggi@caviumnetworks.com | * Manish Jaggi: Manish.Jaggi@caviumnetworks.com | ||
| * Kin-Yip Liu: kin-yip.liu@caviumnetworks.com | * Kin-Yip Liu: kin-yip.liu@caviumnetworks.com | ||
| + | * Prakash Ramchandran: prakash.ramchandran@huawei.com | ||
nfv_hypervisors-kvm.1435536472.txt.gz · Last modified: 2015/06/29 00:07 by Jun Nakajima
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
