Re: [dpdk-dev] [PATCH] crypto/octeontx2: enable unbinding

2020-02-12 Thread Akhil Goyal
> > > > Like for OCTEON TX, the OCTEON TX2 crypto engines must first be unbound > > from their kernel module, then rebound to vfio-pci, before being used in > > DPDK. > > > > As this capability is detected at runtime by dpdk-pmdinfo, add the info in > > the > > PMD registering directives. > > > >

Re: [dpdk-dev] [PATCH] crypto/octeontx2: enable unbinding

2020-02-09 Thread Anoob Joseph
> > Like for OCTEON TX, the OCTEON TX2 crypto engines must first be unbound > from their kernel module, then rebound to vfio-pci, before being used in DPDK. > > As this capability is detected at runtime by dpdk-pmdinfo, add the info in the > PMD registering directives. > > Then an external scrip

[dpdk-dev] [PATCH] crypto/octeontx2: enable unbinding

2020-02-09 Thread Thierry Herbelot
Like for OCTEON TX, the OCTEON TX2 crypto engines must first be unbound from their kernel module, then rebound to vfio-pci, before being used in DPDK. As this capability is detected at runtime by dpdk-pmdinfo, add the info in the PMD registering directives. Then an external script can be used for