diff options
author | Ido Schimmel <idosch@mellanox.com> | 2019-08-11 10:35:51 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-08-11 10:53:30 -0700 |
commit | ca30707dee2bc8bc81cfd8b4277fe90f7ca6df1f (patch) | |
tree | 831109dafd3bf717632f63d5ff1bdac8b3d42527 /MAINTAINERS | |
parent | 28315f7999870bb56da236f6b4ffce63efcc7897 (diff) |
drop_monitor: Add packet alert mode
So far drop monitor supported only one alert mode in which a summary of
locations in which packets were recently dropped was sent to user space.
This alert mode is sufficient in order to understand that packets were
dropped, but lacks information to perform a more detailed analysis.
Add a new alert mode in which the dropped packet itself is passed to
user space along with metadata: The drop location (as program counter
and resolved symbol), ingress netdevice and drop timestamp. More
metadata can be added in the future.
To avoid performing expensive operations in the context in which
kfree_skb() is invoked (can be hard IRQ), the dropped skb is cloned and
queued on per-CPU skb drop list. Then, in process context the netlink
message is allocated, prepared and finally sent to user space.
The per-CPU skb drop list is limited to 1000 skbs to prevent exhausting
the system's memory. Subsequent patches will make this limit
configurable and also add a counter that indicates how many skbs were
tail dropped.
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions