From: Ferruh Yigit <ferruh.yigit@intel.com>
To: 王万臣 <wwcemail@163.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] basicfwd
Date: Fri, 2 Jul 2021 12:56:05 +0200 [thread overview]
Message-ID: <8abe6673-640d-07eb-579b-0d5a4ce57db2@intel.com> (raw)
In-Reply-To: <c612627.5ff7.17a615b51fc.Coremail.wwcemail@163.com>
On 7/1/2021 11:16 AM, 王万臣 wrote:
> Hello, I tried to run a sample program (Skeleton) after installing DPDK according to the Getting Started Guide for Linux document, but failed, "Detected shared linkage of DPDK" is missing in the output of EAL initialization, compared with the correct output result. And the rte_eth_dev_count_avail() function always return 0, even though I've already bound the NIC port for the DPDK driver, so what should I do to solve this problem, thanks!
>
Hi,
Not sure about the problem, can you try with "--log-level *:debug" perhaps
additional log gives additional clue.
prev parent reply other threads:[~2021-07-02 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 9:16 王万臣
2021-07-02 10:56 ` Ferruh Yigit [this message]
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=8abe6673-640d-07eb-579b-0d5a4ce57db2@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=wwcemail@163.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).