DPDK usage discussions
 help / color / mirror / Atom feed
From: Hristo.Trifonov <Hristo.Trifonov@ul.ie>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] port 0 not present on board error
Date: Tue, 12 Dec 2017 12:47:30 +0000	[thread overview]
Message-ID: <E6A390FF2129134EB58BFFFFDFFB5A844DFF28EB@ExMbx1.ul.campus> (raw)

Please use only 2 ports with 1RX queue and 1 TX queue each to get l3fwd running. Try with these 2 below.
0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio unused=vfio-pci
0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' drv=igb_uio unused=vfio-pci

You can use more ports/queues but then you'll have to change the -config option depending on how many cores do you want to use.

The cmd that I've provided in my previous post is specifically for 2 ports with 1RX and TX queue each and 2 cores.

I suggest that you restart your machine, if possible, to unbind all ports from igb_uio and start from scratch.
Otherwise use the dpdk-seup.py script to do the clean-up.

Hristo T.

             reply	other threads:[~2017-12-12 12:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 12:47 Hristo.Trifonov [this message]
2017-12-12 13:33 ` Pragash Vijayaragavan
  -- 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 10:54 Hristo.Trifonov
2017-12-12 12:21 ` Pragash Vijayaragavan
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
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=E6A390FF2129134EB58BFFFFDFFB5A844DFF28EB@ExMbx1.ul.campus \
    --to=hristo.trifonov@ul.ie \
    --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).