[dpdk-dev] pci device access from dpdk secondary process with igb_uio

Hi All, I am trying to use pci vf device with secondary process in a multiple process mode and finding pci_dev->mem_resource[0].addr to be NULL. This happens when the pci device is attached to igb_uio.ko but with vfio_pci it works fine. Looking at the pci device initialization part for secondary p

Re: [dpdk-dev] pci device access from dpdk secondary process with igb_uio

On Thu, 26 Dec 2019 at 16:58, vijay mohan wrote: > > Hi All, > I am trying to use pci vf device with secondary process in a multiple process > mode and finding pci_dev->mem_resource[0].addr to be NULL. This happens when > the pci device is attached to igb_uio.ko but with vfio

Re: [dpdk-dev] [PATCH] bus/pci: pcidev access from secondary process

Hi Thomas, As long as pmd or application doesn't access dev->mem_resource[i].addr, secondary process works with igb_uio. But for pci devices like crypto_qat, pmd checks for dev->mem_resource[i].addr and bails out if the address is null. Root cause is, not initializing the mapped address in rte_pci

Re: [dpdk-dev] pci device access from dpdk secondary process with igb_uio

and send up a patch or will I do that? > > Fiona > > > > -Original Message- > > From: Trahe, Fiona > > Sent: Wednesday, January 22, 2020 5:19 PM > > To: vijay mohan ; dev@dpdk.org; Yigit, Ferruh > > > > Cc: Trahe, Fiona > > Subject: R