Messages in this thread | ![/](/images/icornerl.gif) | | Subject | Re: [Intel-wired-lan] bug with rx-udp-gro-forwarding offloading? | From | Paolo Abeni <> | Date | Mon, 26 Jun 2023 18:42:04 +0200 |
| |
On Mon, 2023-06-26 at 16:25 +0200, Ian Kumlien wrote: > On Mon, Jun 26, 2023 at 4:18 PM Alexander Lobakin > <aleksander.lobakin@intel.com> wrote: > > > > From: Ian Kumlien <ian.kumlien@gmail.com> > > Date: Sun, 25 Jun 2023 12:59:54 +0200 > > > > > It could actually be that it's related to: rx-gro-list but > > > rx-udp-gro-forwarding makes it trigger quicker... I have yet to > > > trigger it on igb > > > > Hi, the rx-udp-gro-forwarding author here. > > > > (good thing this appeared on IWL, which I read time to time, but please > > Cc netdev next time) > > (thus +Cc Jakub, Eric, and netdev) > > Well, two things, it seems like rx-udp-gro-forwarding accelerates it > but the issue is actually in: rx-gro-list > > And since i've only been able to trigger it in ixgbe i thought it > might be a driver issue =) > > > > On Sat, Jun 24, 2023 at 10:03 PM Ian Kumlien <ian.kumlien@gmail.com> wrote: > > > > > > > > Hi again, > > > > > > > > I suspect that I have rounded this down to the rx-udp-gro-forwarding > > > > option... I know it's not on by default but.... > > > > > > > > So, I have a machine with four nics, all using ixgbe, they are all: > > > > 06:00.0 Ethernet controller: Intel Corporation Ethernet Connection > > > > X553 1GbE (rev 11) > > > > 06:00.1 Ethernet controller: Intel Corporation Ethernet Connection > > > > X553 1GbE (rev 11) > > > > 07:00.0 Ethernet controller: Intel Corporation Ethernet Connection > > > > X553 1GbE (rev 11) > > > > 07:00.1 Ethernet controller: Intel Corporation Ethernet Connection > > > > X553 1GbE (rev 11) > > > > > > > > But I have been playing with various... currently i do: > > > > for interface in eno1 eno2 eno3 eno4 ; do > > > > for offload in ntuple hw-tc-offload rx-gro-list ; do > > > > ethtool -K $interface $offload on > /dev/null > > > > done > > > > ethtool -G $interface rx 8192 tx 8192 > /devYnull > > > > done > > > > > > > > And it all seems to work just fine for my little firewall > > > > > > > > However, enabling rx-udp-gro-forwarding results in the attached oooops > > > > (sorry, can't see more, been recreating by watching shows on HBO > > > > max... ) > > > > Where's the mentioned oops? Where's the original message? > > Held by the mailing list since i can only get a screenshot of it... > Will attach the latest one to this email
That image is not very useful/does not provide a lot of relevant information. Could you please use kdump/crash to collect a (decoded) full stack trace?
> (I wish that i could easily get a larger backtrace but i haven't > looked in further atm) > > > Can't this be related to [0]? > > Don't know, my main test has been running video streams in the > background - eventually they cause a oops (within 40 minutes or so) > But i doubt it's counted as tunnel data ;)
I read the above as you don't have UDP tunnels in your setup. Am I correct?
Thanks,
Paolo
| ![\](/images/icornerr.gif) |