From: Im Groot <imgroot2048@gmail.com>
To: users@dpdk.org
Subject: DPDK Window 10: Hello World example Error: Failed to initialize DDP parser
Date: Wed, 15 Nov 2023 17:16:46 +0500 [thread overview]
Message-ID: <CAO-K+9zt=r9umyi11BnYK_aQfMepgX8ZUzLgg2Sux+GsmxQ70Q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1800 bytes --]
Hi
I recently started building a DPDK for window 10 22H2. I was able to build
the virt2phy and netuio driver successfully. I am using DPDK DPDK 22.11.3
(LTS).
- I used visual studio 2019 community edition with WDK and SDK
10.0.22000 as recommended by you. And both drivers were built and
installed successfully. Device manager looks like this:
[image: image.png]
- I have granted lock pages in memory on window 10. I guess this is
supported.
[image: image.png]
- Now I am running the hello world example and I am getting the
following message on cmd. I want to know how I can debug this issue:
[image: image.png]
C:\dpdk\build\examples>dpdk-helloworld.exe -l 0-3
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Multi-process support is requested, but not available.
EAL: Requested device 0000:00:1f.6 cannot be used
EAL: Probe PCI driver: net_ice (8086:159b) device: 0000:01:00.0 (socket -1)
ice_flow_init(): Failed to initialize DDP parser, raw packet filter will
not be supported
EAL: Probe PCI driver: net_ice (8086:159b) device: 0000:01:00.1 (socket -1)
ice_flow_init(): Failed to initialize DDP parser, raw packet filter will
not be supported
hello from core 1
hello from core 2
hello from core 3
hello from core 0
*Questions:*
I have the following queries:
1. What does this error say (hello world example). Is there some issue
with the installation? How can I resolve this issue?
- *EAL: Probe PCI driver: net_ice (8086:159b) device: 0000:01:00.0
(socket -1)*
*ice_flow_init(): Failed to initialize DDP parser, raw packet filter
will not be supported*
2. Does the driver in the device manager look alright?
3. I am using DPDK DPDK 22.11.3 (LTS). Is this the correct version to
use?
Thanks
[-- Attachment #1.2: Type: text/html, Size: 3369 bytes --]
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 84816 bytes --]
[-- Attachment #3: image.png --]
[-- Type: image/png, Size: 28828 bytes --]
[-- Attachment #4: image.png --]
[-- Type: image/png, Size: 29273 bytes --]
next reply other threads:[~2023-11-16 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 12:16 Im Groot [this message]
2023-11-16 7:11 ` Dmitry Kozlyuk
2023-11-16 9:30 ` Zhang, Qi Z
2023-11-17 7:36 ` Im Groot
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='CAO-K+9zt=r9umyi11BnYK_aQfMepgX8ZUzLgg2Sux+GsmxQ70Q@mail.gmail.com' \
--to=imgroot2048@gmail.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).