From: Thenveer Poolakkanni <thenveer.poolakkanni@iwave-global.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"andremue@linux.microsoft.com" <andremue@linux.microsoft.com>,
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Chaturbhuja Nath Prabhu <c.prabhu@iwave-global.com>,
Ayshathul Thuhara <ayshathul.thuhara@iwave-global.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: Assistance with DPDK on Windows
Date: Fri, 14 Nov 2025 10:12:52 +0000 [thread overview]
Message-ID: <PN3P287MB02734300BEDDDD5A08219DCCB7CAA@PN3P287MB0273.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <2455856.MHSsGVy7CF@thomas>
[-- Attachment #1.1: Type: text/plain, Size: 2288 bytes --]
Hi Team,
I have successfully compiled and built DPDK on a Windows system and am using a custom driver in conjunction with DPDK. I am able to write to the registers, and the driver can also read from them. Additionally, I have successfully loaded the netuio driver onto my network interfaces (01:00.0 and 01:00.1).
However, when running the DPDK application, I encounter the following error: "Invalid memory, No probed Ethernet devices." The issue is detailed further in the screenshot below.
[cid:94365efe-78e5-4ef2-9d9a-b49188e35759]
Could you please assist in identifying the cause of this error and advise on potential steps to resolve it?
Thank you in advance for your support.
Best regards,
Thenveer
________________________________
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Wednesday, November 5, 2025 3:55 PM
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 <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
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?
[-- Attachment #1.2: Type: text/html, Size: 4811 bytes --]
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 24340 bytes --]
parent reply other threads:[~2025-11-15 17:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <2455856.MHSsGVy7CF@thomas>]
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=PN3P287MB02734300BEDDDD5A08219DCCB7CAA@PN3P287MB0273.INDP287.PROD.OUTLOOK.COM \
--to=thenveer.poolakkanni@iwave-global.com \
--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=thomas@monjalon.net \
--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).