On Wed, Oct 16, 2019 at 5:07 PM Jerin Jacob <jerinjac...@gmail.com> wrote: > > > > > > > > > > no-iommu case is different where we cannot screw Linux netdev driver, you > > > can create a damage to your self that's an acceptable compromise. > > > > > > In this case, when DPDK PF bound application dies then it will impact > > > netdev VF driver as gets stalled and there is a security issues to VF > > > netdev driver that DPDK PF can intersect the netdev VF mailbox message. > > > > > > So this case is different where from Kernel PoV there is damange to > > > netdev VF so this can not be accepted in Linux. > > > > > > One option is to add this piece of code igb-uio instead to adding new > > > driver. What do you say? > > > > > > It is the problem for all non bifurcated drivers in DPDK not specific to > > > Marvell. > > > > > > The workaround is to use igb-uio with non VFIO. > > > We can not support UIO through performance reason hence we need a > > > solution that works for VFIO due to HW accelerated mempool architecture > > > (applicable for all NPU) > > > > > > We can not have VFIO vs UIO specific features disparity in DPDK. Please > > > have same treatment. Either remove igb-uio hacks from Dpdk or enable non > > > upsteamble features through igb-uio.So that there is no disparity for a > > > specific use case / vendor. > > > > Andrew Rybchenko already acked this patch and I provided enough data > > on the need for this patch. > > I hope there is no more confusion about the need for this patch. > > > I assume no more issue to merge this patch for RC1. If yes, please discuss.
Ping++
