On 11/1/2023 6:02 PM, Stephen Hemminger wrote: > Update the documentation and tools to build the BPF program used by > tap device. And apply fix to the RSS algorithm to correctly > handle non-IP protocols. > > v6 - cosmetic improvements to extract process > add better boilerplate and fix python lint warnings > > Madhuker Mythri (1): > net/tap: Fixed RSS algorithm to support fragmented packets > > Stephen Hemminger (2): > net/tap: support infrastructure to build the BPF filter > net/tap; rebuild and update the BPF flow program >
Thanks Stephen for fixing this. But considering it was broken for a while and nobody complained, and initial developers seems lost interest and it is relatively hard code to maintain, do we still want to keep this support. Can we probe again motivation and benefit of eBPF support in tap PMD, and if it is still relevant?