From: Bruce Richardson <bruce.richardson@intel.com>
To: Pragash Vijayaragavan <pxv3620@rit.edu>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] check_port_config error
Date: Tue, 12 Dec 2017 14:16:00 +0000 [thread overview]
Message-ID: <20171212141600.GB7280@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <CANp7S21yc-JCJwbS2pXcJMpKANkc0jU7hwCCekZ1PaZSLSorkA@mail.gmail.com>
On Tue, Dec 12, 2017 at 01:22:16AM -0500, Pragash Vijayaragavan wrote:
> Hi,
>
> I am trying to run dpdk app l3fwd but gives some errors.
>
> I bind my nics using dpdk-dev-bind script.
>
> I also set env variables correctly.
>
> The nb_ports is 0 when i tried printing that inside "check_port_config"
> function.
> Also I used "igb_uio" module but it still shows net_i40e
>
> can someone help me please. Thanks
>
Hi,
this question is more suited to the users@dpdk.org rather than the
dev@dpdk.org list.
However, in order to debug your problem, it could be useful to send on
the output of "dpdk-devbind.py -s" to show the current state of the
various ports.
> pragash@revvit:~/dpdk-stable-17.05.2/examples/l3fwd/build$ ./l3fwd -l 1-19
> --no-huge -- -p 0x07 -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
I notice too, that you are not running as the root user and not using
hugepage memory. In this case, the driver may not be able to function as
it cannot get the physical address information of the memory in use.
Does running using sudo and without the "--no-huge" flag work?
/Bruce
parent reply other threads:[~2017-12-12 14:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CANp7S21yc-JCJwbS2pXcJMpKANkc0jU7hwCCekZ1PaZSLSorkA@mail.gmail.com>]
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=20171212141600.GB7280@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--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).