Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-1517

Optimise flow extraction wrt tunneled packets

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • openvswitch3.5
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Given openvswitch 3.6+ with offload refactor enabled,

      When a packet is received and not part of a tunnel,

      Then the flow extraction logic avoids unnecessary tunnel branching and inner offset initialization.

      Show
      Given openvswitch 3.6+ with offload refactor enabled, When a packet is received and not part of a tunnel, Then the flow extraction logic avoids unnecessary tunnel branching and inner offset initialization.
    • rhel-9
    • None
    • rhel-net-ovs-dpdk
    • ssg_networking
    • Moderate

      In not yet released OVS 3.6, after the OVS offloads API revamp, there is still one branch in the flow extraction to check if the packet is a tunneled one.

      https://github.com/openvswitch/ovs/blob/1210864a63a0462ac6572b3e2e5ef1aba0060a50/lib/flow.c#L864

      This could be reworked so only "outer" offsets are reset in miniflow_extract, yet initialisation of the inner offsets must be carefully checked in all code leading to a flow extraction.

      Note: since there is no 3.6 downstream package, this ticket is opened against 3.5, for now.

              ovsdpdk-triage ovsdpdk triage
              rhn-support-dmarchan David Marchand
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: