DPDK usage discussions
 help / color / mirror / Atom feed
From: =?gb18030?B?0uy/zQ==?= <zhangjungang_1107@qq.com>
To: =?gb18030?B?dXNlcnM=?= <users@dpdk.org>
Subject: how can let rte_eal_init parse device success?
Date: Tue, 29 Aug 2023 16:45:25 +0800	[thread overview]
Message-ID: <tencent_B091FF4EB220DF38EFEAD2EE7ED7DDDE0109@qq.com> (raw)

[-- 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 --]

             reply	other threads:[~2023-08-29  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29  8:45 =?gb18030?B?0uy/zQ==?= [this message]
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==?=

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_B091FF4EB220DF38EFEAD2EE7ED7DDDE0109@qq.com \
    --to=zhangjungang_1107@qq.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).