diff options
| author | Daniel Borkmann <daniel@iogearbox.net> | 2018-11-09 09:16:32 +0100 |
|---|---|---|
| committer | Daniel Borkmann <daniel@iogearbox.net> | 2018-11-09 09:16:33 +0100 |
| commit | 185067a86a789e490ab4e1bb97b97fb3e2c40066 (patch) | |
| tree | d89f4a220e92ba787649adc101d2e7861791539d /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | bpf_load: add map name to load_maps error message (diff) | |
| parent | nfp: bpf: relax prog rejection through max_pkt_offset (diff) | |
| download | linux-185067a86a789e490ab4e1bb97b97fb3e2c40066.tar.gz linux-185067a86a789e490ab4e1bb97b97fb3e2c40066.zip | |
Merge branch 'bpf-max-pkt-offset'
Jiong Wang says:
====================
The maximum packet offset accessed by one BPF program is useful
information.
Because sometimes there could be packet split and it is possible for some
reasons (for example performance) we want to reject the BPF program if the
maximum packet size would trigger such split. Normally, MTU value is
treated as the maximum packet size, but one BPF program does not always
access the whole packet, it could only access the head portion of the data.
We could let verifier calculate the maximum packet offset ever used and
record it inside prog auxiliar information structure as a new field
"max_pkt_offset".
====================
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions