diff options
| author | Judy Hsiao <[email protected]> | 2023-12-06 03:38:33 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2023-12-08 10:37:43 +0000 |
| commit | e5dc5afff62f3e97e86c3643ec9fcad23de4f2d3 (patch) | |
| tree | e4c14162082802b8f862a108210a038b3aa69b99 /net/ipv4/tcp_input.c | |
| parent | 179a8b515e4b8971ae4ad2db36a44f0691fc6756 (diff) | |
neighbour: Don't let neigh_forced_gc() disable preemption for long
We are seeing cases where neigh_cleanup_and_release() is called by
neigh_forced_gc() many times in a row with preemption turned off.
When running on a low powered CPU at a low CPU frequency, this has
been measured to keep preemption off for ~10 ms. That's not great on a
system with HZ=1000 which expects tasks to be able to schedule in
with ~1ms latency.
Suggested-by: Douglas Anderson <[email protected]>
Signed-off-by: Judy Hsiao <[email protected]>
Reviewed-by: David Ahern <[email protected]>
Reviewed-by: Eric Dumazet <[email protected]>
Reviewed-by: Douglas Anderson <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'net/ipv4/tcp_input.c')
0 files changed, 0 insertions, 0 deletions