> > > > > > > There is security issue in attaching DPDK PF driver and netdev bind to VF. > > So this scheme is not upsteamble to Linux kernel. Since rte_flow had VF > > action. We need this scheme to support VF action with VFIO. So, Out of tree > > is the only way as it is DPDK specific feature. Already sent patches to > > Linux kernel, it make sense to not accept this in upstream. We are already > > exposing such features through igb-uio for non VFIO device. IMO, there > > should not be any disparity between igb-uio and VFIO in DPDK. > > > > If we are against out of tree module, let's remove igb-uio as well. We > > can't have different treatment for similar issues. > > You are right igb-uio is legacy and only exists for users unwilling to > change (such as old kernels which don't support vfio noiommu mode). > Eventually it should go as well. And the same for KNI.
+ Techboard I understand, Everyone would like not to have out of tree kernel modules in dpdk repo. Is it possible to a) move existing or new out of tree module or b) libraries can be used by another project or c) DPDK device drivers binary FW repo like Linux kernel FW etc(The ones connected to dpdk) add it in https://www.dpdk.org/hosted-projects/ and use tools like "https://gerrit.googlesource.com/git-repo/"[1] for development and distribution case [1] git-repo: tools used by android for a similar situation.
