Epic Goal

• Move DPDK & RDMA support from TP to GA

Why is this important?

• Customer wants to build supported solution based on DPDK & RDMA techniques.

Use Case

As a developer of high-throughput data plane traffic applications, I need SR-IOV’s RDMA and DPDK modes to support networking workloads with low latency, high bandwidth, and low CPU consumption requirements that may have GPU-powered cross-cluster distributed workflows and require the ability to read/write memory directly on a remote cluster node (e.g. AI/ML Deep Learning).
 

Acceptance Criteria

• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

Previous Work (Optional):

1. DPDK & RDMA with SR-IOV has been TP supported since 4.3

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement https://docs.google.com/presentation/d/13wM3wV8NhJgPEChTJypJ4KGri2EMTz72zpaz9XM5xJg/edit?usp=sharing 
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: https://github.com/openshift/openshift-docs/pull/36335 https://github.com/openshift/openshift-docs/pull/36336
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>