[dpdk-dev] [PATCH 00/10] Infrastructure to detect iova mapping on the bus

[santosh]

Hi Thomas,

On Tuesday 04 July 2017 12:49 PM, Thomas Monjalon wrote:

> 04/07/2017 06:41, santosh:
>> Ping?
> You should try to ping Sergio, memory maintainer,
> and Anatoly, VFIO maintainer.
>
> Given that
> - there is no review at all,

By default if no review then its maintainer responsibility to review Or 
ask someone to review?

BTW: Who is the bus maintainer? I don't see entry in MAINTAINER file.

> - it is conflicting with the bus/PCI rework in progress,
> it will not be considered for 17.08.

We're adding only two new iommu_class bus api in rte_bus, I'm not sure
about conflict. If there is conflict then I should see review comment for
same in my patch set?

This initiatives came out from [1], and we put lot of effort in
breaking down api from bus till library layer. This framework indeed
a need for those platform which cares for iova=va like octeontx, dpaa2 and
perhaps many future SoCs. W/o this framework, we can't get pktio working for octeontx ethdev 
in dpdk, can't get HW pool manager working for Octeontx offload blocks.

I agree that I missed on sergio or Anatoly But crux of design is rte_bus
layer. I expect comment on those area, right?

And if we have consent on bus approach then rest changes are trivial.

I didn't ping before as You had picked my patch set and asked for review comment in past.

Can we include it in RC2? Because it will delay upstreaming effort of octeontx ethdev driver
and other dependent driver for us.

Thanks.