DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Pragash Vijayaragavan <pxv3620@rit.edu>
Cc: "Hristo.Trifonov" <Hristo.Trifonov@ul.ie>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] port 0 not present on board error
Date: Mon, 11 Dec 2017 23:17:09 -0800	[thread overview]
Message-ID: <20171211231709.618fdf40@xeon-e3> (raw)
In-Reply-To: <CANp7S23LfN=FeirjhFP9B0LaV+1z_hOq+CMmv2vwr0CJAHHnYg@mail.gmail.com>

On Mon, 11 Dec 2017 16:24:18 -0500
Pragash Vijayaragavan <pxv3620@rit.edu> wrote:

> $ ./l3fwd -l 1-4
> --no-huge -- -p 0x3 -L --config="(0,0,1),(1,0,2)" --ipv6 --parse-ptype
> EAL: Detected 20 lcore(s)
> EAL: Probing VFIO support...
> EAL: Started without hugepages support, physical addresses not available

Try setting up huge pages, that can help.

> EAL: PCI device 0000:02:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: Requested device 0000:02:00.0 cannot be used

Since you are using VFIO, that implies IOMMU support.
With IOMMU on some systems the IOMMU channels overlap groups.
See Linux kernel documentation vfio.txt for more information on how
VFIO works and how to map out groups.

When a device is in a group with another device, you must
assign or unbind both devices in order for VFIO-PCI to work.
On one system, I had unbind (which disabled) the on board NIC
in order to use VFIO with a 10G or 40G device in the PCI-E slot
since both NIC's shared the same group.

Unfortunately, the easiest solution is just to find another
system since this is a wiring/motherboard issue not something
controlled by OS or BIOS.


> EAL: PCI device 0000:02:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: PCI device 0000:04:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: Requested device 0000:04:00.0 cannot be used
> EAL: PCI device 0000:04:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1583 net_i40e
> EAL: PCI device 0000:08:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:08:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> L3FWD: Longest-prefix match selected
> L3FWD: IPV6 is specifiednsoft parse-ptype is enabled
> port 0 is not present on the board

  parent reply	other threads:[~2017-12-12  7:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 11:21 Hristo.Trifonov
2017-12-11 21:24 ` Pragash Vijayaragavan
2017-12-12  6:17   ` Pragash Vijayaragavan
2017-12-12  7:17   ` Stephen Hemminger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-12 14:02 Hristo.Trifonov
2017-12-12 14:13 ` Pragash Vijayaragavan
2017-12-12 12:47 Hristo.Trifonov
2017-12-12 13:33 ` Pragash Vijayaragavan
2017-12-12 10:54 Hristo.Trifonov
2017-12-12 12:21 ` Pragash Vijayaragavan
2017-12-08 12:11 Hristo.Trifonov
2017-12-08 20:22 ` Pragash Vijayaragavan
2017-12-08  4:01 Pragash Vijayaragavan
2017-12-08  4:18 ` Dave Boutcher
2017-12-08  4:21   ` Pragash Vijayaragavan

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=20171211231709.618fdf40@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=Hristo.Trifonov@ul.ie \
    --cc=pxv3620@rit.edu \
    --cc=users@dpdk.org \
    /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).