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

[ERFE] Add support for TC tunnel flag matching

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • rhel-8, rhel-9
    • openvswitch3.3
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • rhel-net-ovs-dpdk
    • ssg_networking
    • OVS/DPDK - FDP 24.H
    • 1

      Currently, the following patch is proposed upstream:

       

      [net-next,v2,0/2] net: allow dissecting/matching tunnel control flags
      Davide Caratti Feb. 1, 2024, 4:51 p.m. UTC
      Ilya says: "for correct matching on decapsulated packets, we should match on not only tunnel id and headers, but also on tunnel configuration flags like TUNNEL_NO_CSUM and TUNNEL_DONT_FRAGMENT. This is done to distinguish similar tunnels with slightly different configs. And it is important since tunnel configuration is flow based, i.e. can be different for every packet, even though the main tunnel port is the same." 
      - patch 1 extends the kernel's flow dissector to extract these flags    from the packet's tunnel metadata.  
      - patch 2 extends TC flower to match on any combination of TUNNEL_NO_CSUM,    TUNNEL_OAM and TUNNEL_DONT_FRAGMENT.
      

      First question is; will this patch be useful for OVS and easy to apply?

      Second, if it is, we should prepare an upstream patch.

              echaudro@redhat.com Eelco Chaudron
              echaudro@redhat.com Eelco Chaudron
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: