diff options
author | 2019-12-13 17:43:33 -0800 | |
---|---|---|
committer | 2019-12-15 15:58:05 -0800 | |
commit | eba9c5f498a11a8558e099d14692c24f2fea27e3 (patch) | |
tree | 3fc0077c3d890005efcc5e456f19780376991c54 /MAINTAINERS | |
parent | libbpf: Expose BPF program's function name (diff) | |
download | linux-dev-eba9c5f498a11a8558e099d14692c24f2fea27e3.tar.xz linux-dev-eba9c5f498a11a8558e099d14692c24f2fea27e3.zip |
libbpf: Refactor global data map initialization
Refactor global data map initialization to use anonymous mmap()-ed memory
instead of malloc()-ed one. This allows to do a transparent re-mmap()-ing of
already existing memory address to point to BPF map's memory after
bpf_object__load() step (done in follow up patch). This choreographed setup
allows to have a nice and unsurprising way to pre-initialize read-only (and
r/w as well) maps by user and after BPF map creation keep working with
mmap()-ed contents of this map. All in a way that doesn't require user code to
update any pointers: the illusion of working with memory contents is preserved
before and after actual BPF map instantiation.
Selftests and runqslower example demonstrate this feature in follow up patches.
Signed-off-by: Andrii Nakryiko <andriin@fb.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Martin KaFai Lau <kafai@fb.com>
Link: https://lore.kernel.org/bpf/20191214014341.3442258-10-andriin@fb.com
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions