Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-118120

RTE FLOW with RAW pattern will not work using E810

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • rhel-9.6.z
    • dpdk
    • No
    • Important
    • rhel-net-drivers-2
    • None
    • Hide

      Oct 7 - Assigned with Intel devs and will check with DPDK team.  

      Show
      Oct 7 - Assigned with Intel devs and will check with DPDK team.  
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      What were you trying to do that didn't work?

      Deploying a DPDK v23 application that leverages RTE FLOW with RAW pattern. Code can be reviewed here: https://github.com/cdonatom/dpdk_rte_flow/blob/master/src/mac_swap_forward_rte.c

      What is the impact of this issue to you?

      This behaviour conflicts: https://issues.redhat.com/browse/RHEL-92770

      Please provide the package NVR for which the bug is seen:

      More info:

      [core@cloudransno-site1 ~]$ sudo ethtool -i enp84s0

      driver: ice version: 5.14.0-570.41.1.el9_6.x86_64

      firmware-version: 4.01 0x800135e6 1.3256.0

      expansion-rom-version:

      bus-info: 0000:54:00.0

      supports-statistics: yes

      supports-test: yes

      supports-eeprom-access: yes

      supports-register-dump: yes

      supports-priv-flags: yes

      How reproducible is this bug?:

      Using RHCOS 9.6.20250908-0 with the kernel 5.14.0-570.41.1.el9_6.x86_64 deploy the following image: https://quay.io/repository/cdonato/dpdk_rte_raw 

      Steps to reproduce

      1. Deploy OCP 4.20-rc.2 using ZTP with Telco profile
      2. Deploy the following workload: https://quay.io/repository/cdonato/dpdk_rte_raw  (I can provide access to the automation)
      3. Wait for the pod to come up and crash

      Expected results

      Container starts forwarding L2 packets using the RAW pattern

      Actual results

      iavf can't create the RAW pattern rule

      Defaulted container "t32-1" out of: t32-1, t32-2, t32-3, t32-4, sidecar-1, t32-5, t32-init (ini
      EAL: Detected CPU cores: 64
      EAL: Detected NUMA nodes: 1
      EAL: Detected shared linkage of DPDK
      EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
      EAL: Selected IOVA mode 'VA'
      EAL: No available 2048 kB hugepages reported
      EAL: VFIO support initialized
      EAL: Using IOMMU type 1 (Type 1)
      EAL: Probe PCI driver: net_lavf
      (8086:1889) device: 0000:54:01.3 (socket 0)
      EAL: Probe PCI driver: net_iavf
      (8086:1889) device: 0000:54:01.5 (socket 0)
      TELEMETRY: No legacy callbacks, legacy socket not created
      iavf_configure_queues (): request RXDID[22] in Queue [0]
      iavf_flow_create(): Failed to create flow
      Failed to create RAW flow: Failed to create parser engine.
      EAL: Error - exiting with code: 1
      Cause: Failed to setup RAW rte_flow
      Port 0 MAC: 0E:93:4D: F0:49:2D

              aleksandr.loktionov@intel.com aleksandr Loktionov
              cdonato@redhat.com Carlos Donato
              Intel Confidential Group
              ovsdpdk triage ovsdpdk triage
              Jiying Qiu Jiying Qiu
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: