From: Thomas Monjalon <thomas@monjalon.net>
To: "andremue@linux.microsoft.com" <andremue@linux.microsoft.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: Thenveer Poolakkanni <thenveer.poolakkanni@iwave-global.com>,
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, 05 Nov 2025 11:25:43 +0100 [thread overview]
Message-ID: <2455856.MHSsGVy7CF@thomas> (raw)
In-Reply-To: <85f9def5-7f88-47d1-9dc8-524b060c54e5@gmail.com>
05/11/2025 08:36, Dmitry Kozlyuk:
> 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.
This question is probably showing a lack of documentation.
Please can we have this gap solved with a patch?
next prev parent reply other threads:[~2025-11-05 10:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 7:18 Assistance with DPDK on Windows Thenveer Poolakkanni
2025-11-05 7:36 ` Dmitry Kozlyuk
2025-11-05 10:25 ` Thomas Monjalon [this message]
2025-11-14 10:12 ` Thenveer Poolakkanni
2025-12-01 5:55 ` Thenveer Poolakkanni
2025-12-01 9:13 ` Thenveer Poolakkanni
2025-12-01 9:20 ` Dmitry Kozlyuk
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=2455856.MHSsGVy7CF@thomas \
--to=thomas@monjalon.net \
--cc=andremue@linux.microsoft.com \
--cc=ayshathul.thuhara@iwave-global.com \
--cc=c.prabhu@iwave-global.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.