> On Jan 9, 2019, at 5:22 PM, Daniel Waddington <daniel.wadding...@ibm.com> 
> wrote:
> 
> This NIC (000:01:00.0) is supported (Intel XL710). I assume that I can use 
> VFIO instead of UIO. UIO is really bad from a security perspective.
> 
> I think its the "cannot create new DMA window, error 22" which is the first 
> indicator of the problem.
> 
> Daniel
> 
> -----"Wiles, Keith" <keith.wi...@intel.com> wrote: -----
> To: Daniel Waddington <daniel.wadding...@ibm.com>
> From: "Wiles, Keith" <keith.wi...@intel.com>
> Date: 01/09/2019 02:52PM
> Cc: "dev@dpdk.org" <dev@dpdk.org>
> Subject: Re: [dpdk-dev] DPDK on IBM Power9
> 
> 
>> On Jan 9, 2019, at 4:25 PM, Daniel Waddington <daniel.wadding...@ibm.com> 
>> wrote:
>> 
>> Hi,
>> I'm trying to run DPDK 18.11 on IBM Power9.  Should it run?  (I'n new to 
>> DPDK on Power). 
>> Thx,
>> Daniel
>> Below is what I get:
>> 
>> $ sudo ./examples/ethtool/ethtool-app/ppc_64-power8-linuxapp-gcc/app/ethtool 
>> --iova-mode=pa -c7 -w 0000:01:00.0
>> EAL: Detected 128 lcore(s)
>> EAL: Detected 2 NUMA nodes
>> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
>> EAL: Probing VFIO support...
>> EAL: VFIO support initialized
>> EAL: PCI device 0000:01:00.0 on NUMA socket 0
>> EAL:   probe driver: 8086:1583 net_i40e
>> EAL:   using IOMMU type 7 (sPAPR)
>> EAL:   cannot create new DMA window, error 22 (Invalid argument)
>> EAL: Could not create new DMA window
>> EAL:   0000:01:00.0 DMA remapping failed, error 22 (Invalid argument)
>> EAL: Requested device 0000:01:00.0 cannot be used
>> Number of NICs: 0
>> EAL: Error - exiting with code: 1
>> Cause: No available NIC ports!
>> 
> 
> From the message above you need support NIC for DPDK is all or you a NIC 
> needs to be bound to something like igb_uio for linux. I have never run DPDK 
> on power before and not sure what is next other then using a supported NIC.
> 

Yes you should be able to use VFIO. Did you bind the NIC to VFIO ?

There should be some docs about how that is done.

Beyond this I have not idea?
>> 
>> 
> 
> Regards,
> Keith
> 
> 

Regards,
Keith

Reply via email to