From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Thenveer Poolakkanni <thenveer.poolakkanni@iwave-global.com>,
"andremue@linux.microsoft.com" <andremue@linux.microsoft.com>
Cc: dev <dev@dpdk.org>,
Chaturbhuja Nath Prabhu <c.prabhu@iwave-global.com>,
Ayshathul Thuhara <ayshathul.thuhara@iwave-global.com>
Subject: Re: Assistance with DPDK on Windows
Date: Wed, 5 Nov 2025 10:36:37 +0300 [thread overview]
Message-ID: <85f9def5-7f88-47d1-9dc8-524b060c54e5@gmail.com> (raw)
In-Reply-To: <PN3P287MB0273982789E89005206DA9B0B7C4A@PN3P287MB0273.INDP287.PROD.OUTLOOK.COM>
Hi Thenveer,
On 11/5/25 10:18, Thenveer Poolakkanni wrote:
> 1. Is it possible to execute or use dpdk-devbind.py on Windows to
> verify the device binding status?
No. Please use Device Manager for now.
> 2. On Windows, the build generates .dll files (e.g.,
> rte_net_driver.dll) instead of .so files (e.g., librte_net_driver.so
> in Linux). How can we use or execute these .dll files in the same way
> we use .so files when running DPDK applications?
>
The application must link the needed libraries and PMDs when building.
These files must be in PATH or in the working directory when running the
application. Loading additional PMDs with "-d" EAL option is not yet
implemented. If you have a custom PMD you have to build it as a part of
DPDK and link to your application.
P. S. Questions like these belong to users@dpdk.org. Keeping in dev@ to
avoid breaking threads.
next prev parent reply other threads:[~2025-11-05 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 7:18 Thenveer Poolakkanni
2025-11-05 7:36 ` Dmitry Kozlyuk [this message]
2025-11-05 10:25 ` Thomas Monjalon
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=85f9def5-7f88-47d1-9dc8-524b060c54e5@gmail.com \
--to=dmitry.kozliuk@gmail.com \
--cc=andremue@linux.microsoft.com \
--cc=ayshathul.thuhara@iwave-global.com \
--cc=c.prabhu@iwave-global.com \
--cc=dev@dpdk.org \
--cc=thenveer.poolakkanni@iwave-global.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).