[Kernel-packages] [Bug 1868113] Comment bridged from LTC Bugzilla

2020-03-31 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2020-03-31 09:58 EDT--- IBM Bugzilla status-> closed, Fix Released with focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868113

[Kernel-packages] [Bug 1868113] Comment bridged from LTC Bugzilla

2020-03-30 Thread bugproxy
--- Comment From danijel.so...@de.ibm.com 2020-03-30 08:43 EDT--- Hi, I think this suggestion is fine, let us do it as the first step. We may discuss later on what our options are in regards of enabling architecture-specific tunings in distros. Cheers, Danijel -- You received this bug n

[Kernel-packages] [Bug 1868113] Comment bridged from LTC Bugzilla

2020-03-26 Thread bugproxy
--- Comment From danijel.so...@de.ibm.com 2020-03-26 06:29 EDT--- Hi, our intention was *never* to revert a patch. What we propose is to trigger the mentioned ethtool command (ethtool --set-priv-flags DEVNAME rx_striding_rq on) as soon as the distro is running on a z14/z15 machine and the

[Kernel-packages] [Bug 1868113] Comment bridged from LTC Bugzilla

2020-03-24 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2020-03-24 04:25 EDT--- After all the discussion , please default ConnectX-4 back to striding RQ when using a z14/z15, even it could be set by the ethtool. Many thanks in advance -- You received this bug notification because you are a membe

[Kernel-packages] [Bug 1868113] Comment bridged from LTC Bugzilla

2020-03-23 Thread bugproxy
--- Comment From danijel.so...@de.ibm.com 2020-03-20 06:01 EDT--- Hi, first let me get to your questions regarding the kernel. As you already guessed, this was an upstream (fedora) kernel and the latest version at the time we pursued the issue. That is also the answer to why we did not