On Fri, Dec 28, 2018 at 10:03:01AM -0800, Gregory Rose wrote: > > On 12/27/2018 1:38 PM, Gregory Rose wrote: > > > >On 12/27/2018 11:40 AM, Ben Pfaff wrote: > >>Greg, this is a kernel issue. If you have the time, will you take a > >>look at it sometime? > > > >Yep, will do. > > > >- Greg > > I looked into this and there is not much for us to do wrt our kernel > datapath. It is a kernel GRO fix and if it > is not in the kernel you're using then you'll have to talk to your vendor > about getting the fix into their next > distribution kernel package upgrade or else roll (i.e. custom build) your > own kernel. > > I checked all the recent 3.10.x kernel sources using the lexer at > access.redhat.com and did not find any > of them that carried Lorenzo's fix (commit 8e1da73acded on Dave Miller's > current net tree) all the way > up to 3.10.0-957.el7. That is RHEL 7.6 and is the latest so it looks like > RHEL 7 is stuck with the bug.
Does it make sense to point out the issue to someone appropriate at Red Hat so that they can consider applying the fix? _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
