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

When the interface type is dpdk, runtime_data_ovs_interface_handler will always trigger a recompute.

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • OVN
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Given a system with the runtime_data_ovs_interface_handler configured to handle various interface types,

      When the interface type is dpdkvhostuserclient,

      Then the is_iface_vif function should correctly recognize the dpdkvhostuserclient type and not trigger a recompute unnecessarily.

      Show
      Given a system with the runtime_data_ovs_interface_handler configured to handle various interface types, When the interface type is dpdkvhostuserclient, Then the is_iface_vif function should correctly recognize the dpdkvhostuserclient type and not trigger a recompute unnecessarily.
    • None
    • rhel-net-ovn
    • ssg_networking

      This is a known issue being tracked in the following GitHub OVN issue, #174. The issue states the following:

      when iface type is dpdk type, the runtime_data_ovs_interface_handler will always trigger recompute. {_}
      {}
      {}Because is_iface_vif function not consider the dpdk type, so untime_data_ovs_interface_handler will always trigger recompute. When the logical flows is too much, will impact on network delay.{_}

              amusil@redhat.com Ales Musil
              echaudro@redhat.com Eelco Chaudron
              Jianlin Shi Jianlin Shi
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: