Re: [dpdk-dev] [PATCH v3 01/11] eal/pci: introduce PCI driver iova as va flag

2017-07-11 Thread Maxime Coquelin
On 07/11/2017 12:35 PM, santosh wrote: Hi Maxime, On Tuesday 11 July 2017 02:39 PM, Maxime Coquelin wrote: On 07/11/2017 08:16 AM, Santosh Shukla wrote: Introducing RTE_PCI_DRV_NEED_IOVA_VA flag. Flag used when driver needs to operate in iova=va mode. Why driver need iova=va mapping? On

Re: [dpdk-dev] [PATCH v3 01/11] eal/pci: introduce PCI driver iova as va flag

2017-07-11 Thread santosh
Hi Maxime, On Tuesday 11 July 2017 02:39 PM, Maxime Coquelin wrote: > > > On 07/11/2017 08:16 AM, Santosh Shukla wrote: >> Introducing RTE_PCI_DRV_NEED_IOVA_VA flag. Flag used when driver needs >> to operate in iova=va mode. >> >> Why driver need iova=va mapping? >> >> On NPU style co-processors

Re: [dpdk-dev] [PATCH v3 01/11] eal/pci: introduce PCI driver iova as va flag

2017-07-11 Thread Maxime Coquelin
On 07/11/2017 08:16 AM, Santosh Shukla wrote: Introducing RTE_PCI_DRV_NEED_IOVA_VA flag. Flag used when driver needs to operate in iova=va mode. Why driver need iova=va mapping? On NPU style co-processors like Octeontx, the buffer recycling has been done in HW, unlike SW model. Here is the da

[dpdk-dev] [PATCH v3 01/11] eal/pci: introduce PCI driver iova as va flag

2017-07-10 Thread Santosh Shukla
Introducing RTE_PCI_DRV_NEED_IOVA_VA flag. Flag used when driver needs to operate in iova=va mode. Why driver need iova=va mapping? On NPU style co-processors like Octeontx, the buffer recycling has been done in HW, unlike SW model. Here is the data flow: 1) On control path, Fill the HW mempool w