diff options
author | Cong Wang <[email protected]> | 2021-02-23 10:49:28 -0800 |
---|---|---|
committer | Alexei Starovoitov <[email protected]> | 2021-02-26 12:28:03 -0800 |
commit | 16137b09a66f2b75090f1e56a9ba0e27ef845ebc (patch) | |
tree | 84e6f4a946e33b2654e36b3563d3488c27ac9f13 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
parent | 5a685cd94b21a88efa6be77169eddef525368034 (diff) |
bpf: Compute data_end dynamically with JIT code
Currently, we compute ->data_end with a compile-time constant
offset of skb. But as Jakub pointed out, we can actually compute
it in eBPF JIT code at run-time, so that we can competely get
rid of ->data_end. This is similar to skb_shinfo(skb) computation
in bpf_convert_shinfo_access().
Suggested-by: Jakub Sitnicki <[email protected]>
Signed-off-by: Cong Wang <[email protected]>
Signed-off-by: Alexei Starovoitov <[email protected]>
Acked-by: John Fastabend <[email protected]>
Acked-by: Jakub Sitnicki <[email protected]>
Link: https://lore.kernel.org/bpf/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions