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 10:54:09 +0000 [thread overview]
Message-ID: <E6A390FF2129134EB58BFFFFDFFB5A844DFF2663@ExMbx1.ul.campus> (raw)
If your nb_ports = 0 shows that you haven't bind/provided any ports to dpdk.
Just verify that the ports that you want to use with dpdk (igb_uio) are available on the machine.
This means that they are not used for anything else but dpdk.
Before you attempt to bind any ports to igb_uio, from the terminal check what ports are available on the machine using nmcli d or any other utility.
Load the igb_uio kernel module using the dpdk_setup script in dpdk/usertools
Then use the dpdk_dev_bind or dpdk_setup script to bind the selected ports to igb_uio.
Verify that the ports are using the igb_uio with the dpdk_setup script. There is an option there for that.
If you are using 2 ports (-p 0x3), use 2 lcores (-c 0xE) core 2 and core 3 in this case.
Complete the cmd like this:
pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$<mailto:pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$> ./l3fwd -c 0xE --no-huge -- -p 0x03 -L --config="(0,0,1),(1,0,2)" --parse-ptype
If you want to use more lcores you must then change the -config option to reflect the situation in terms of (port,queue,lcore)
Hristo T.
next reply other threads:[~2017-12-12 10:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 10:54 Hristo.Trifonov [this message]
2017-12-12 12:21 ` 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 12:47 Hristo.Trifonov
2017-12-12 13:33 ` 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=E6A390FF2129134EB58BFFFFDFFB5A844DFF2663@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).