diff options
author | Breno Leitao <leitao@debian.org> | 2024-10-08 19:32:04 +0300 |
---|---|---|
committer | Paolo Abeni <pabeni@redhat.com> | 2024-10-10 12:57:34 +0300 |
commit | 9e542ff8b79ae1871074d3a7dca7de9e7374eeda (patch) | |
tree | 956f9480806e1e6558470152cf6fc9f7d27f1865 /tools/perf/scripts/python/stackcollapse.py | |
parent | 09cf85ef183a5603db49d542264ddbece3258e55 (diff) | |
download | linux-9e542ff8b79ae1871074d3a7dca7de9e7374eeda.tar.xz |
net: Remove likely from l3mdev_master_ifindex_by_index
The likely() annotation in l3mdev_master_ifindex_by_index() has been
found to be incorrect 100% of the time in real-world workloads (e.g.,
web servers).
Annotated branches shows the following in these servers:
correct incorrect % Function File Line
0 169053813 100 l3mdev_master_ifindex_by_index l3mdev.h 81
This is happening because l3mdev_master_ifindex_by_index() is called
from __inet_check_established(), which calls
l3mdev_master_ifindex_by_index() passing the socked bounded interface.
l3mdev_master_ifindex_by_index(net, sk->sk_bound_dev_if);
Since most sockets are not going to be bound to a network device,
the likely() is giving the wrong assumption.
Remove the likely() annotation to ensure more accurate branch
prediction.
Signed-off-by: Breno Leitao <leitao@debian.org>
Reviewed-by: David Ahern <dsahern@kernel.org>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Link: https://patch.msgid.link/20241008163205.3939629-1-leitao@debian.org
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions