Hi Alex,
On 11/18/17 11:20 AM, Alex Williamson wrote:
On Fri, 17 Nov 2017 14:51:52 -0700
Alex Williamson wrote:
On Fri, 17 Nov 2017 15:11:19 -0600
Suravee Suthikulpanit wrote:
From: Suravee Suthikulpanit
VFIO IOMMU type1 currently upmaps IOVA pages synchronously, which requires
IOTLB flus
Hi Alex,
On 11/18/17 4:51 AM, Alex Williamson wrote:
On Fri, 17 Nov 2017 15:11:19 -0600
Suravee Suthikulpanit wrote:
From: Suravee Suthikulpanit
VFIO IOMMU type1 currently upmaps IOVA pages synchronously, which requires
IOTLB flushing for every unmapping. This results in large IOTLB flushing
On Fri, 17 Nov 2017 14:51:52 -0700
Alex Williamson wrote:
> On Fri, 17 Nov 2017 15:11:19 -0600
> Suravee Suthikulpanit wrote:
>
> > From: Suravee Suthikulpanit
> >
> > VFIO IOMMU type1 currently upmaps IOVA pages synchronously, which requires
> > IOTLB flushing for every unmapping. This resul
On Fri, 17 Nov 2017 15:11:19 -0600
Suravee Suthikulpanit wrote:
> From: Suravee Suthikulpanit
>
> VFIO IOMMU type1 currently upmaps IOVA pages synchronously, which requires
> IOTLB flushing for every unmapping. This results in large IOTLB flushing
> overhead when handling pass-through devices w
From: Suravee Suthikulpanit
VFIO IOMMU type1 currently upmaps IOVA pages synchronously, which requires
IOTLB flushing for every unmapping. This results in large IOTLB flushing
overhead when handling pass-through devices with a large number of mapped
IOVAs (e.g. GPUs).
This can be avoided by usin