diff options
| author | Daniel Borkmann <[email protected]> | 2022-05-25 00:56:18 +0200 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2022-05-25 22:00:48 -0700 |
| commit | ed6cd6a17896561b9f51ab4c0d9bbb29e762b597 (patch) | |
| tree | 48d0d7fa93663bc51c4295279a2ccfd34dd14768 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | b3b1a17538d3ef6a9667b2271216fd16d7678ab5 (diff) | |
net, neigh: Set lower cap for neigh_managed_work rearming
Yuwei reported that plain reuse of DELAY_PROBE_TIME to rearm work queue
in neigh_managed_work is problematic if user explicitly configures the
DELAY_PROBE_TIME to 0 for a neighbor table. Such misconfig can then hog
CPU to 100% processing the system work queue. Instead, set lower interval
bound to HZ which is totally sufficient. Yuwei is additionally looking
into making the interval separately configurable from DELAY_PROBE_TIME.
Reported-by: Yuwei Wang <[email protected]>
Signed-off-by: Daniel Borkmann <[email protected]>
Link: https://lore.kernel.org/netdev/[email protected]
Reviewed-by: Nikolay Aleksandrov <[email protected]>
Link: https://lore.kernel.org/r/3b8c5aa906c52c3a8c995d1b2e8ccf650ea7c716.1653432794.git.daniel@iogearbox.net
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions