Re: [dpdk-dev] [PATCH v1 1/1] vfio: add page-by-page mapping API

2021-10-28 Thread Burakov, Anatoly
On 28-Oct-21 9:18 AM, David Marchand wrote: On Wed, Sep 29, 2021 at 12:19 PM Burakov, Anatoly wrote: @@ -2179,7 +2208,29 @@ rte_vfio_container_dma_map(int container_fd, uint64_t vaddr, uint64_t iova, return -1; } - return container_dma_map(vfio_cfg, vaddr, iova, len)

Re: [dpdk-dev] [PATCH v1 1/1] vfio: add page-by-page mapping API

2021-10-28 Thread David Marchand
On Wed, Sep 29, 2021 at 12:19 PM Burakov, Anatoly wrote: > > @@ -2179,7 +2208,29 @@ rte_vfio_container_dma_map(int container_fd, > > uint64_t vaddr, uint64_t iova, > > return -1; > > } > > > > - return container_dma_map(vfio_cfg, vaddr, iova, len); > > + /* not having

Re: [dpdk-dev] [PATCH v1 1/1] vfio: add page-by-page mapping API

2021-09-29 Thread Burakov, Anatoly
On 10-Sep-21 12:27 PM, Anatoly Burakov wrote: Currently, there is no way to map memory for DMA in a way that allows unmapping it partially later, because some IOMMU's do not support partial unmapping. There is a workaround of mapping all of these segments separately, but this is inconvenient and

Re: [dpdk-dev] [PATCH v1 1/1] vfio: add page-by-page mapping API

2021-09-10 Thread Burakov, Anatoly
On 10-Sep-21 12:27 PM, Anatoly Burakov wrote: Currently, there is no way to map memory for DMA in a way that allows unmapping it partially later, because some IOMMU's do not support partial unmapping. There is a workaround of mapping all of these segments separately, but this is inconvenient and

[dpdk-dev] [PATCH v1 1/1] vfio: add page-by-page mapping API

2021-09-10 Thread Anatoly Burakov
Currently, there is no way to map memory for DMA in a way that allows unmapping it partially later, because some IOMMU's do not support partial unmapping. There is a workaround of mapping all of these segments separately, but this is inconvenient and silly, so this commit adds a proper API that doe