Please backport openvswitch-switch and friends

[Kees Meijs <kees@nefos.nl>]

    Hi there,
    
    We extensively use Open vSwitch in our OpenStack and
    Ceph environments and noticed version 2.10 "eats up" a CPU core with
    100% utilisation on buster.
    
    For example:
    
> 2020-01-19T23:00:06.362Z|148220|poll_loop(handler130)|INFO|Dropped
>       734849 log messages in last 6 seconds (most recently, 0 seconds
>       ago) due to excessive rate
>       2020-01-19T23:00:06.362Z|148221|poll_loop(handler130)|INFO|wakeup
>       due to [POLLIN] on fd 23 (unknown anon_inode:[eventpoll]) at
>       lib/dpif-netlink.c:2786 (99% CPU usage)
>     
    
    Other users experience a similar problem on other distributions as
    well. As it seems this is a bug resolved in version 2.11.
    
    This morning I manually built the 2.11 package from bullseye and
    installed that. Although the build is not perfect (needed to add
    some files to debian/not-installed from bugtool) the resulting
    packages install well and the CPU usage is back to normal values.
    
    For reference, I added the following files:
    
> usr/share/openvswitch/bugtool-plugins/system-configuration.xml
> usr/share/openvswitch/bugtool-plugins/system-configuration/openvswitch.xml
>       usr/share/openvswitch/bugtool-plugins/system-logs/openvswitch.xml
>       usr/share/openvswitch/bugtool-plugins/kernel-info/openvswitch.xml
> usr/share/openvswitch/bugtool-plugins/network-status/openvswitch.xml
>       usr/share/openvswitch/bugtool-plugins/network-status/ovn.xml
>     
    
    Other than that, backporting seems trivial.
    
    What do you think is the way to go? Bump to version 2.11 on buster
    since it's only a minor version change or is someone willing to add
    2.11 to buster-backports?
    
    Thanks in advance!
    
    Best regards,
    Kees

--
https://nefos.nl/contact

Nefos IT bv
Ambachtsweg 25 (industrienummer 4217)
5627 BZ Eindhoven
Nederland

KvK 66494931

Aanwezig op maandag, dinsdag, woensdag en vrijdag