I think it has a interesting option `ethtool -K ethX ntuple [on|offwhich is interesting has the knowledge , we can keep it as a part the main task .
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 19 2024
Another note—our current RPS implementation intentionally excludes core 0 from packet processing. If we want the default RSS behavior to mimic, this might mean we should be using N-1 queues where N is the number of cores. Whether this makes sense to carry over to RSS I'll leave open for debate.
Should RSS/ntuple be the default or should it be an opt-in "offload" setting?
Ack, I'm inclined to close this as a duplicate. What's the best way to mark the ticket?
this task is already created, it involved many offload/NIC tunning which are described on this :
Doesn't cloud-init fully cover this? We are provisioning our VPN endpoints fully via that and thus never need to touch the device once it is running. You need to provide an according config file + .iso at initial boot though, which might only be feasible when VyOS runs inside a VM.
Aug 18 2024
Merged PR: https://github.com/vyos/vyos-1x/pull/3992
Aug 17 2024
Aug 16 2024
Aug 15 2024
Aug 14 2024
This can likely wait for backport until some feedback is received on useful additions.
Aug 13 2024
I've seen this a few times on the most recent 1.5x rolling releases. So far every stack trace has included the xfrm_input kernel function, so this tells me it is likely specific to when QAT is combined with the VTI feature (which switched from the vti interface type to xfrm type in 1.4).
Aug 12 2024
Might be related patches (no idea if they have anything to do with the kernel panics seen in 6.6):
I have the same problem, disable QAT also worked in my case. QAT drivers before 4.24 are working. So VyOS 1.4.0 is also affected
Config to reproduce the issue: