Device iotlb: Difference between revisions
From KVM
| Line 5: | Line 5: | ||
This page provides information about the design of Device IOTLB for vhost-net to provides a secure and efficient environment for dpdk like program in guest. | This page provides information about the design of Device IOTLB for vhost-net to provides a secure and efficient environment for dpdk like program in guest. | ||
== Design == | == Design Goals == | ||
=== Architecture Independent === | |||
The implementation should be compatible to current Qemu's IOMMU architecture, then it should be architecture independent and then be easy to be ported to various platform/IOMMU implementation. | |||
=== Efficient === | |||
End user should have no obvious felling performance degradation when using dpdk like program in guest. | |||
=== Compatible === | |||
The implementation should be compatible to current vhost-net memory region API to support VM without DMAR enabled. | |||
Revision as of 03:46, 4 February 2016
Vhost-net Device IOTLB
Overview
This page provides information about the design of Device IOTLB for vhost-net to provides a secure and efficient environment for dpdk like program in guest.
Design Goals
Architecture Independent
The implementation should be compatible to current Qemu's IOMMU architecture, then it should be architecture independent and then be easy to be ported to various platform/IOMMU implementation.
Efficient
End user should have no obvious felling performance degradation when using dpdk like program in guest.
Compatible
The implementation should be compatible to current vhost-net memory region API to support VM without DMAR enabled.