* how can let rte_eal_init parse device success?
@ 2023-08-29 8:45 =?gb18030?B?0uy/zQ==?=
2023-08-29 9:18 ` Dmitry Kozlyuk
0 siblings, 1 reply; 4+ messages in thread
From: =?gb18030?B?0uy/zQ==?= @ 2023-08-29 8:45 UTC (permalink / raw)
To: =?gb18030?B?dXNlcnM=?=
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 225 bytes --]
devbind sucess
lspci is right
then rte eal init can't parse dev "69:00.0"
but the dpdk test tool is ok to run rte eal init
the try ./helloworld -a "69:00.0" also rte eal init failed;
BR.
[-- Attachment #2: Type: text/html, Size: 405 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how can let rte_eal_init parse device success?
2023-08-29 8:45 how can let rte_eal_init parse device success? =?gb18030?B?0uy/zQ==?=
@ 2023-08-29 9:18 ` Dmitry Kozlyuk
2023-08-29 9:53 ` =?gb18030?B?0uy/zQ==?=
0 siblings, 1 reply; 4+ messages in thread
From: Dmitry Kozlyuk @ 2023-08-29 9:18 UTC (permalink / raw)
To: 异客; +Cc: users
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".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how can let rte_eal_init parse device success?
2023-08-29 9:18 ` Dmitry Kozlyuk
@ 2023-08-29 9:53 ` =?gb18030?B?0uy/zQ==?=
2023-08-30 7:07 ` =?gb18030?B?ob5DbG9zZWShv1JlcGx5Ly+72Li0o7ogaG93IGNhbiBsZXQgcnRlX2VhbF9pbml0IHBhcnNlIGRldmljZSBzdWNjZXNzPw==?= =?gb18030?B?0uy/zQ==?=
0 siblings, 1 reply; 4+ messages in thread
From: =?gb18030?B?0uy/zQ==?= @ 2023-08-29 9:53 UTC (permalink / raw)
To: =?gb18030?B?RG1pdHJ5IEtvemx5dWs=?=; +Cc: =?gb18030?B?dXNlcnM=?=
[-- 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 --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* =?gb18030?B?ob5DbG9zZWShv1JlcGx5Ly+72Li0o7ogaG93IGNhbiBsZXQgcnRlX2VhbF9pbml0IHBhcnNlIGRldmljZSBzdWNjZXNzPw==?=
2023-08-29 9:53 ` =?gb18030?B?0uy/zQ==?=
@ 2023-08-30 7:07 ` =?gb18030?B?0uy/zQ==?=
0 siblings, 0 replies; 4+ messages in thread
From: =?gb18030?B?0uy/zQ==?= @ 2023-08-30 7:07 UTC (permalink / raw)
To: =?gb18030?B?RG1pdHJ5IEtvemx5dWs=?=; +Cc: =?gb18030?B?dXNlcnM=?=
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset="gb18030", Size: 2888 bytes --]
Hi all,
The issue has been resloved, I missing some lib at my env!
Thanks for your time~
Regards!
------------------ ÔʼÓʼþ ------------------
·¢¼þÈË: "Òì¿Í" <zhangjungang_1107@qq.com>;
·¢ËÍʱ¼ä: 2023Äê8ÔÂ29ÈÕ(ÐÇÆÚ¶þ) ÏÂÎç5:53
ÊÕ¼þÈË: "Dmitry Kozlyuk"<dmitry.kozliuk@gmail.com>;
³ËÍ: "users"<users@dpdk.org>;
Ö÷Ìâ: Re: how can let rte_eal_init parse device success?
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: 4704 bytes --]
[-- Attachment #2: DFC880CD@2BF8FC61.BAEAEE64.jpg --]
[-- Type: image/jpeg, Size: 3234 bytes --]
[-- Attachment #3: A8D1FBFA@EE06030D.BAEAEE64.jpg --]
[-- Type: image/jpeg, Size: 19003 bytes --]
[-- Attachment #4: 199A7BD2@877EB836.BAEAEE64.jpg --]
[-- Type: image/jpeg, Size: 14199 bytes --]
[-- Attachment #5: B0957C2A@41934A74.BAEAEE64.jpg --]
[-- Type: image/jpeg, Size: 22699 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-08-30 7:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-29 8:45 how can let rte_eal_init parse device success? =?gb18030?B?0uy/zQ==?=
2023-08-29 9:18 ` Dmitry Kozlyuk
2023-08-29 9:53 ` =?gb18030?B?0uy/zQ==?=
2023-08-30 7:07 ` =?gb18030?B?ob5DbG9zZWShv1JlcGx5Ly+72Li0o7ogaG93IGNhbiBsZXQgcnRlX2VhbF9pbml0IHBhcnNlIGRldmljZSBzdWNjZXNzPw==?= =?gb18030?B?0uy/zQ==?=
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).