Challenges and Gaps in OvS-DPDK Acceleration

Download Presenatation
Challenges and Gaps in OvS-DPDK Acceleration
Slide Note
Embed
Share

OvS-DPDK faces architecture and implementation gaps in offload capability discovery and flow validation, lacking support for certain actions and management interfaces. There is a need to address dynamic rebalancing, error reporting, and integration with Openstack/OVN to enhance acceleration and offload efficiency.

  • OvS-DPDK
  • Acceleration
  • Gaps
  • Offload
  • Challenges

Uploaded on Apr 04, 2025 | 1 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. December 10-11, 2019 | Westford, MA OvS-DPDK Acceleration with rte_flow: Challenges and Gaps Dr. Hemal V. Shah and Sriharsha Basavapatna, Broadcom Inc.

  2. OvS-DPDK Acceleration Architecture Gaps Offload capability missing discovery rte_flow_validate: to validate a flow for offload Issues: extra operation, lack of specific error info OvS-DPDK does not even use rte_flow_validate Need to optimize design for capability discovery Challenges with offload on vhost-user port Actions offload is not supported for ingress flows Software lookup is needed for egress flows Actions offload is also not supported for egress flows DPDK VF Representor (VF-Rep) management plane CLI or management I/F does not exist VF creation/destruction is outside of DPDK environment PF PMD can t be used for VF management Vendor specific creation/destruction of VF-Rep A possible fix: dedicate a VF PMD for VF-Reps mgmt

  3. OvS-DPDK Acceleration Implementation Gaps Actions Offload (partial and full) Supported: MARK, RSS Not supported: OUTPUT, DROP, COUNT, VF, ENCAP, DECAP, METER, etc. Control Plane APIs Supported: Add, Delete Not supported: Dump, Flush, Stat Recent full offload patches try to address this No error reporting for offloaded flows Need to refine

  4. Other OvS-DPDK Offload Considerations Dynamic Rebalance does not exist, needed for capacity mgmt. Kernel and user/dpdk datapath differ w.r.t offloads kernel/tc : flow added to either DP or HW dpdk: flow added to both DP and HW Impacts dynamic rebalancing logic need consistency Leverage Out-Of-Resources (ENOSPC) error reporting from PMDs Need error propagation from dpif-netdev back to ofproto-dpif Openstack/OVN Integration Let us advance and improve OvS-DPDK acceleration/offload.

More Related Content