diff options
| author | Judy Hsiao <judyhsiao@chromium.org> | 2023-12-06 03:38:33 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-01-20 11:50:07 +0100 |
| commit | f379394a78a0ded98029505e3efa83d0605d4246 (patch) | |
| tree | 8b999a90e4e3ba41c880690ece8870423eed3256 /drivers/platform | |
| parent | 9b5044e17e1e3a95c33eb629c0c474e3b4bc515b (diff) | |
| download | linux-f379394a78a0ded98029505e3efa83d0605d4246.tar.gz linux-f379394a78a0ded98029505e3efa83d0605d4246.tar.bz2 linux-f379394a78a0ded98029505e3efa83d0605d4246.zip | |
neighbour: Don't let neigh_forced_gc() disable preemption for long
[ Upstream commit e5dc5afff62f3e97e86c3643ec9fcad23de4f2d3 ]
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 <dianders@chromium.org>
Signed-off-by: Judy Hsiao <judyhsiao@chromium.org>
Reviewed-by: David Ahern <dsahern@kernel.org>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/platform')
0 files changed, 0 insertions, 0 deletions