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

Add MTU Oversize Message To OVS

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • ovs-dpdk
    • None
    • Add MTU Oversize Message To OVS
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      ( ) The epics work is available in a downstream build (nightly/async or other)

      ( ) Test coverage is available in downstream CI if applicable

      ( ) All cards under the epic have been moved to Done

      ( ) Failed Test Plans have bugs added as children to the epic/feature.

      Show
      Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. ( ) The epics work is available in a downstream build (nightly/async or other) ( ) Test coverage is available in downstream CI if applicable ( ) All cards under the epic have been moved to Done ( ) Failed Test Plans have bugs added as children to the epic/feature.
    • rhel-net-ovs-dpdk
    • 100% To Do, 0% In Progress, 0% Done
    • ssg_networking

      This epic tracks all the effort needed to deliver the solution related to the feature request described below.
      Orig Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2040815
      Description of problem:
      There is no log message generated in the case of an ovs port, bridge, etc which drops a packet because of an oversize MTU.

      How reproducible:
      Create a KVM instance using the Virtio driver and configure the MTU larger than bridge or port the instance is attached and send packets larger than this egress interface. Nothing will be logged on the KVM hypervisor.

      Expected results:
      Expect the hypervisor to log a message to kernel ring buffer.

      Additional info:
      There has been some work suggested for other driver like the Intel i40 driver.
      https://www.spinics.net/lists/netdev/msg719280.html

       

       
      So I assume this needs to be assigned to the hypervisor team? Or do we need something specific from the kernel driver, then it needs to go to the Kernel team?

      Maxime as this might be more in your area, can you add a comment, and re-assign it to the correct team?

              ovsdpdk-bot ovsdpdk bot
              jfargen@redhat.com Jamie Fargen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: