diff options
author | 2022-03-20 18:59:00 -0700 | |
---|---|---|
committer | 2022-03-20 18:59:00 -0700 | |
commit | 46e9244b2563cc53acc63b57f5eb2999fa729c60 (patch) | |
tree | a68caed04866465d23d56a0ce32220741231745a /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Merge branch 'Enable non-atomic allocations in local storage' (diff) | |
parent | selftests/bpf: Fix test for 4-byte load from remote_port on big-endian (diff) | |
download | linux-dev-46e9244b2563cc53acc63b57f5eb2999fa729c60.tar.xz linux-dev-46e9244b2563cc53acc63b57f5eb2999fa729c60.zip |
Merge branch 'Make 2-byte access to bpf_sk_lookup->remote_port endian-agnostic'
Jakub Sitnicki says:
====================
This patch set is a result of a discussion we had around the RFC patchset from
Ilya [1]. The fix for the narrow loads from the RFC series is still relevant,
but this series does not depend on it. Nor is it required to unbreak sk_lookup
tests on BE, if this series gets applied.
To summarize the takeaways from [1]:
1) we want to make 2-byte load from ctx->remote_port portable across LE and BE,
2) we keep the 4-byte load from ctx->remote_port as it is today - result varies
on endianess of the platform.
[1] https://lore.kernel.org/bpf/20220222182559.2865596-2-iii@linux.ibm.com/
v1 -> v2:
- Remove needless check that 4-byte load is from &ctx->remote_port offset
(Martin)
[v1]: https://lore.kernel.org/bpf/20220317165826.1099418-1-jakub@cloudflare.com/
====================
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions