tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

net: Kconfig: discourage drop_monitor enablement

Quoting Eric Dumazet:
"I do not understand the fascination with net/core/drop_monitor.c [..]
misses all the features, flexibility, scalability that 'perf',
eBPF tracing, bpftrace, .... have today."

Reword DROP_MONITOR kconfig help text to clearly state that its not
related to perf-based drop monitoring and that its safe to disable
this unless support for the older netlink-based tools is needed.

Signed-off-by: Florian Westphal <fw@strlen.de>
Reviewed-by: Simon Horman <horms@kernel.org>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Link: https://patch.msgid.link/20251016115147.18503-1-fw@strlen.de
Signed-off-by: Jakub Kicinski <kuba@kernel.org>

authored by

Florian Westphal and committed by
Jakub Kicinski 2af8ff1e 38f3cd37

+4 -4
+4 -4
net/Kconfig
··· 400 400 module will be called pktgen. 401 401 402 402 config NET_DROP_MONITOR 403 - tristate "Network packet drop alerting service" 403 + tristate "Legacy network packet drop alerting service" 404 404 depends on INET && TRACEPOINTS 405 405 help 406 406 This feature provides an alerting service to userspace in the 407 407 event that packets are discarded in the network stack. Alerts 408 408 are broadcast via netlink socket to any listening user space 409 - process. If you don't need network drop alerts, or if you are ok 410 - just checking the various proc files and other utilities for 411 - drop statistics, say N here. 409 + process. This feature is NOT related to "perf" based drop monitoring. 410 + Say N here unless you need to support older userspace tools like 411 + "dropwatch". 412 412 413 413 endmenu # Network testing 414 414