From: =?gb18030?B?0uy/zQ==?= <zhangjungang_1107@qq.com>
To: =?gb18030?B?RG1pdHJ5IEtvemx5dWs=?= <dmitry.kozliuk@gmail.com>
Cc: =?gb18030?B?dXNlcnM=?= <users@dpdk.org>
Subject: Re: how can let rte_eal_init parse device success?
Date: Tue, 29 Aug 2023 17:53:22 +0800 [thread overview]
Message-ID: <tencent_118FFE82B2EADE80EFBED2A27F39DC580009@qq.com> (raw)
In-Reply-To: <20230829121836.322f0290@sovereign>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset="gb18030", Size: 2250 bytes --]
Hi Kozlyuk
Tks for your reply
Related info is :
[root@localhost usertools]# ./dpdk-devbind.py -s
Network devices using DPDK-compatible driver
============================================
0000:01:00.1 'I350 Gigabit Network Connection 1521' drv=igb_uio unused=igb,uio_pci_generic
0000:18:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' drv=uio_pci_generic unused=ixgbe,igb_uio
Network devices using kernel driver
===================================
0000:01:00.0 'I350 Gigabit Network Connection 1521' if=em3 drv=igb unused=igb_uio,uio_pci_generic *Active*
0000:18:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection 10fb' if=em2 drv=ixgbe unused=igb_uio,uio_pci_generic
No 'Baseband' devices detected
==============================
No 'Crypto' devices detected
============================
No 'Eventdev' devices detected
==============================
No 'Mempool' devices detected
=============================
No 'Compress' devices detected
==============================
No 'Misc (rawdev)' devices detected
===================================
No 'Regex' devices detected
===========================
then try run dpdk test, it's OK
then run the example:
I think the configuration is ok, it is "dpdk-helloworld" binary.
Regards!
------------------ Original ------------------
From: "Dmitry Kozlyuk" <dmitry.kozliuk@gmail.com>;
Date: Tue, Aug 29, 2023 05:18 PM
To: "Òì¿Í"<zhangjungang_1107@qq.com>;
Cc: "users"<users@dpdk.org>;
Subject: Re: how can let rte_eal_init parse device success?
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".
[-- Attachment #1.2: Type: text/html, Size: 3693 bytes --]
[-- Attachment #2: FC98692E@D6A86805.12C0ED64.png.jpg --]
[-- Type: image/jpeg, Size: 22699 bytes --]
[-- Attachment #3: 62663864@6408C97F.12C0ED64.png.jpg --]
[-- Type: image/jpeg, Size: 14199 bytes --]
[-- Attachment #4: C3642E61@5BDE0A43.12C0ED64.png.jpg --]
[-- Type: image/jpeg, Size: 19003 bytes --]
[-- Attachment #5: 2924DE5A@EFB6691F.12C0ED64.png.jpg --]
[-- Type: image/jpeg, Size: 3234 bytes --]
next prev parent reply other threads:[~2023-08-29 10:03 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
2023-08-29 9:53 ` =?gb18030?B?0uy/zQ==?= [this message]
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=tencent_118FFE82B2EADE80EFBED2A27F39DC580009@qq.com \
--to=zhangjungang_1107@qq.com \
--cc=dmitry.kozliuk@gmail.com \
--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).