From: Ido Schimmel <ido...@idosch.org> Date: Sat, 17 Aug 2019 16:28:09 +0300
> Users have several ways to debug the kernel and understand why a packet > was dropped. For example, using drop monitor and perf. Both utilities > trace kfree_skb(), which is the function called when a packet is freed > as part of a failure. The information provided by these tools is > invaluable when trying to understand the cause of a packet loss. > > In recent years, large portions of the kernel data path were offloaded > to capable devices. Today, it is possible to perform L2 and L3 > forwarding in hardware, as well as tunneling (IP-in-IP and VXLAN). > Different TC classifiers and actions are also offloaded to capable > devices, at both ingress and egress. > > However, when the data path is offloaded it is not possible to achieve > the same level of introspection since packets are dropped by the > underlying device and never reach the kernel. > > This patchset aims to solve this by allowing users to monitor packets > that the underlying device decided to drop along with relevant metadata > such as the drop reason and ingress port. ... Looks great, series applied, thanks.
