From: "Daniel Waddington" <Daniel.Waddington@ibm.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK on IBM Power9
Date: Wed, 9 Jan 2019 23:22:15 +0000 [thread overview]
Message-ID: <OF8C97C6F7.0B9CC43C-ON0025837D.00806190-0025837D.00806196@notes.na.collabserv.com> (raw)
In-Reply-To: <73991857-48DE-4FE9-9798-045C42AC7B1C@intel.com>
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.wiles@intel.com> wrote: -----
To: Daniel Waddington <Daniel.Waddington@ibm.com>
From: "Wiles, Keith" <keith.wiles@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.Waddington@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.
>
>
Regards,
Keith
next prev parent reply other threads:[~2019-01-09 23:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 22:25 Daniel Waddington
2019-01-09 22:52 ` Wiles, Keith
2019-01-09 23:22 ` Daniel Waddington [this message]
2019-01-09 23:35 ` Wiles, Keith
2019-01-09 23:58 ` Daniel Waddington
2019-01-10 0:07 ` Thomas Monjalon
2019-01-10 0:23 ` Wiles, Keith
2019-01-10 7:40 ` Olga Shern
2019-01-10 8:51 ` Burakov, Anatoly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF8C97C6F7.0B9CC43C-ON0025837D.00806190-0025837D.00806196@notes.na.collabserv.com \
--to=daniel.waddington@ibm.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).