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 <[email protected]>
Sent: Wednesday, November 5, 2025 3:55 PM
To: [email protected] <[email protected]>; Dmitry Kozlyuk 
<[email protected]>
Cc: Thenveer Poolakkanni <[email protected]>; [email protected] 
<[email protected]>; Chaturbhuja Nath Prabhu <[email protected]>; Ayshathul 
Thuhara <[email protected]>
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 [email protected]. 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?


Reply via email to