Displaying 3 results from an estimated 3 matches for "tlb_sync".
Did you mean:
iotlb_sync
2018 Jun 26
0
[PATCH v2 0/5] Add virtio-iommu driver
...gt; * Switch to v0.7 of the spec, which changes resv_mem parameters and adds
> an MMIO flag. These are trivial but not backward compatible. Once
> device or driver is upstream, updates to the spec will rely on feature
> bits to stay compatible with this code.
> * Implement the new tlb_sync interface, by splitting add_req() and
> sync_req(). I noticed a small improvement on netperf stream because
> the synchronous iommu_unmap() also benefits from this. Other
> experiments, such as using kmem_cache for requests instead of kmalloc,
> didn't show any improvement....
2018 Jun 21
11
[PATCH v2 0/5] Add virtio-iommu driver
...to fix a build failure?
* Switch to v0.7 of the spec, which changes resv_mem parameters and adds
an MMIO flag. These are trivial but not backward compatible. Once
device or driver is upstream, updates to the spec will rely on feature
bits to stay compatible with this code.
* Implement the new tlb_sync interface, by splitting add_req() and
sync_req(). I noticed a small improvement on netperf stream because
the synchronous iommu_unmap() also benefits from this. Other
experiments, such as using kmem_cache for requests instead of kmalloc,
didn't show any improvement.
Driver is available...
2018 Jun 21
11
[PATCH v2 0/5] Add virtio-iommu driver
...to fix a build failure?
* Switch to v0.7 of the spec, which changes resv_mem parameters and adds
an MMIO flag. These are trivial but not backward compatible. Once
device or driver is upstream, updates to the spec will rely on feature
bits to stay compatible with this code.
* Implement the new tlb_sync interface, by splitting add_req() and
sync_req(). I noticed a small improvement on netperf stream because
the synchronous iommu_unmap() also benefits from this. Other
experiments, such as using kmem_cache for requests instead of kmalloc,
didn't show any improvement.
Driver is available...