DPDK on Window 10 with Intel E810 ERROR: currently package doesn't support RXDID (22)

DPDK on Window 10 with Intel E810 ERROR: currently package doesn't support RXDID (22)

[Im Groot]

[-- Attachment #1.1: Type: text/plain, Size: 7916 bytes --]

I recently ran the skeleton example on window 10:
https://doc.dpdk.org/guides/sample_app_ug/skeleton.html

I got the following error:
[image: image.png]
C:\dpdk\build\examples>dpdk-skeleton.exe
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
ice_program_hw_rx_queue(): currently package doesn't support RXDID (22)
ice_rx_queue_start(): fail to program RX queue 0
ice_dev_start(): fail to start Rx queue 0
EAL: Error - exiting with code: 1
  Cause: Cannot init port 0



I ran the l2fwd example and got the following error:
https://doc.dpdk.org/guides/sample_app_ug/l2_forward_real_virtual.html
[image: image.png]
C:\dpdk\build\examples>dpdk-l2fwd.exe -l 0-3 -n 4 -- -q 8 -p 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
MAC updating enabled
Lcore 0: RX port 0 TX port 1
Lcore 0: RX port 1 TX port 0
Initializing port 0... ice_program_hw_rx_queue(): currently package doesn't
support RXDID (22)
ice_rx_queue_start(): fail to program RX queue 0
ice_dev_start(): fail to start Rx queue 0
EAL: Error - exiting with code: 1
  Cause: rte_eth_dev_start:err=-5, port=0

*************************************************************************************************************************************************************************************
*Issue:*
How can I resolve this issue for window 10:

Initializing port 0... ice_program_hw_rx_queue(): currently package doesn't
support RXDID (22)
ice_rx_queue_start(): fail to program RX queue 0
ice_dev_start(): fail to start Rx queue 0
EAL: Error - exiting with code: 1



*Responses:*

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
I search the error log and found this in dpdk mail archive:
https://www.mail-archive.com/users@dpdk.org/msg05761.html

It has the same error but on linux. And the entire solution was also
provided w.r.t linux. So I have no idea what would be the solution for
window 10.
As per the solution, *ice.pkg* files need to be installed but those files
only work on linux i guess. and so there is no solution for window 10, i
believe.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Recently @Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> mentioned on the same
error that:

"

I'm afraid this might be a big limitation of E810 (net/ice):


https://doc.dpdk.org/guides/nics/ice.html#limitations-or-known-issues


The page says DPP (ice.pkg) loading is required for the NIC to work,
but loading it is not yet supported on Windows,
so I'm not even sure that this NIC is currently usable for DPDK on Windows.
The best next step is to wait for replies from Intel people
(I've replied to your message in users@dpdk.org to invite them).
They enabled this PMD on Windows, so they probably tested it---
maybe there's some extra option required.


"

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

I also contacted someone from microsoft and he said that:

"

These aren’t really Windows specific errors so I’m not sure I have any
useful insight.



Based on the mail thread you linked though it looks like you might try
getting Intel’s latest driver package for the E810, I guess the driver
package probably also includes a firmware update that might bring it into
alignment with what the ice pmd expects.



I have recently used E810 devices in our laboratory and I do recall they
did upgrade the adapters to the latest firmware when the machines were
provisioned for me but I don’t know which firmware or where they downloaded
it from.
"

///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

*Notes:*
Now based on the above I have made the following notes: (correct or not can
be argued...)

   1. DPDK is not supported with full capacity on Windows 10 for the E810
   card.
   2. Based on Intel guide (617015), I can see that they have mentioned
   that without DDP there are very little capabilities available but without
   the DDP the card can still process data. Good thing is that I only need UDP
   for now and I guess it is supported:
   " A general purpose DDP package is automatically installed with all
   supported 800 Series drivers on Windows, ESX, FreeBSD, and Linux operating
   systems, including those provided by the Data Plane Development Kit (DPDK).
   This general purpose DDP package is known as the OS-Default package.
   Additional DDP packages will be available to address packet processing
   needs for specific market segments. For example, a telecommunications
   (Comms) DDP package has been developed to support GTP and PPPoE protocols
   in addition to the protocols in the OS-Default package. The Comms DDP
   package is available with DPDK 19.11 and will also be supported by the 800
   Series ice driver on Linux operating systems."

                                                                        *--
   Introduction, Page 5, 617015, Intel Document*
   [image: image.png]

                                                                          * --
   How DDP Works, Page 7, 617015, Intel Document*
   3. The E810 limitation is not on windows but because of the firmware
   installed on the E810 card. And that E810 firmware can be updated but HOW
   and form WHERE (files)? I fformware can be updated by the end user, I can
   get the full capabilities working on Windows 10 I assume?
   4. I am sure that there is a work around this problem but I am very new
   to DPDK and hence can not proceed without an expert agreeing on it.


*Questions:*

   1. Is there any way to proceed with E810 without DDP even for the basic
   functionality such as UDP?
   2. Is there a way to update the E810 firmware so that DDP can be
   supported on window 10? Or may be any other software approach on Windows 10
   that can solve this issue?
   3. What card should I use next that supports DDP on Windows 10 and I can
   get to achieve the required results?
   4. Can anyone who has run DPDK on window 10 suggest some NIC cards?
   5. I have a doubt that I might be doing something wrong in the
   installation. Such as; I have not installed the E810 card drivers and just
   installed the Netuio and Virt2Phy drivers. (Maybe in the default E810
   window drivers, some DDP files are available that I can use for DPDK)?

Waiting for some good news....

Thanks

[-- Attachment #1.2: Type: text/html, Size: 11546 bytes --]

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 39022 bytes --]

[-- Attachment #3: image.png --]
[-- Type: image/png, Size: 30324 bytes --]

[-- Attachment #4: image.png --]
[-- Type: image/png, Size: 326555 bytes --]