From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: 异客 <zhangjungang_1107@qq.com>
Cc: "users" <users@dpdk.org>
Subject: Re: how can let rte_eal_init parse device success?
Date: Tue, 29 Aug 2023 12:18:36 +0300 [thread overview]
Message-ID: <20230829121836.322f0290@sovereign> (raw)
In-Reply-To: <tencent_B091FF4EB220DF38EFEAD2EE7ED7DDDE0109@qq.com>
Hi,
Most likely PCI bus driver (a DPDK library) is missing.
Either it is not linked into "helloworld" if it is your own app;
or the path to DPDK libraries (*.so) is not in LD_LIBARY_PATH
if it is "dpdk-helloworld" binary.
If this doesn't help, please post exact commands and their full output (log),
not just "success" or "is right".
next prev parent reply other threads:[~2023-08-29 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 8:45 =?gb18030?B?0uy/zQ==?=
2023-08-29 9:18 ` Dmitry Kozlyuk [this message]
2023-08-29 9:53 ` =?gb18030?B?0uy/zQ==?=
2023-08-30 7:07 ` =?gb18030?B?ob5DbG9zZWShv1JlcGx5Ly+72Li0o7ogaG93IGNhbiBsZXQgcnRlX2VhbF9pbml0IHBhcnNlIGRldmljZSBzdWNjZXNzPw==?= =?gb18030?B?0uy/zQ==?=
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=20230829121836.322f0290@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=users@dpdk.org \
--cc=zhangjungang_1107@qq.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).