From: John Fastabend <john.fastabend@gmail.com>
To: Andrii Nakryiko <andriin@fb.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
daniel@iogearbox.net
Cc: andrii.nakryiko@gmail.com, kernel-team@fb.com,
Andrii Nakryiko <andriin@fb.com>
Subject: RE: [PATCH v3 bpf-next 2/3] libbpf: make global data internal arrays mmap()-able, if possible
Date: Wed, 13 Nov 2019 12:21:39 -0800 [thread overview]
Message-ID: <5dcc65d33bdfa_14082b1d9b77e5b4eb@john-XPS-13-9370.notmuch> (raw)
In-Reply-To: <20191113031518.155618-3-andriin@fb.com>
Andrii Nakryiko wrote:
> Add detection of BPF_F_MMAPABLE flag support for arrays and add it as an extra
> flag to internal global data maps, if supported by kernel. This allows users
> to memory-map global data and use it without BPF map operations, greatly
> simplifying user experience.
>
> Acked-by: Song Liu <songliubraving@fb.com>
> Signed-off-by: Andrii Nakryiko <andriin@fb.com>
> ---
[...]
> /*
> @@ -856,8 +858,6 @@ bpf_object__init_internal_map(struct bpf_object *obj, enum libbpf_map_type type,
> pr_warn("failed to alloc map name\n");
> return -ENOMEM;
> }
> - pr_debug("map '%s' (global data): at sec_idx %d, offset %zu.\n",
> - map_name, map->sec_idx, map->sec_offset);
>
> def = &map->def;
> def->type = BPF_MAP_TYPE_ARRAY;
> @@ -865,6 +865,12 @@ bpf_object__init_internal_map(struct bpf_object *obj, enum libbpf_map_type type,
> def->value_size = data->d_size;
> def->max_entries = 1;
> def->map_flags = type == LIBBPF_MAP_RODATA ? BPF_F_RDONLY_PROG : 0;
> + if (obj->caps.array_mmap)
> + def->map_flags |= BPF_F_MMAPABLE;
> +
> + pr_debug("map '%s' (global data): at sec_idx %d, offset %zu, flags %x.\n",
> + map_name, map->sec_idx, map->sec_offset, def->map_flags);
> +
> if (data_buff) {
> *data_buff = malloc(data->d_size);
> if (!*data_buff) {
> @@ -2160,6 +2166,27 @@ static int bpf_object__probe_btf_datasec(struct bpf_object *obj)
> return 0;
> }
I was a bit concerned we should fall back to making the call without the
BPF_F_MMAPABLE flag set if it fails but did a quick walk through the call
path and it seems like it shouldn't fail except if vmalloc/vzalloc failures
so seems fine.
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev parent reply other threads:[~2019-11-13 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 3:15 [PATCH v3 bpf-next 0/3] Add support for memory-mapping BPF array maps Andrii Nakryiko
2019-11-13 3:15 ` [PATCH v3 bpf-next 1/3] bpf: add mmap() support for BPF_MAP_TYPE_ARRAY Andrii Nakryiko
2019-11-13 20:06 ` John Fastabend
2019-11-13 20:41 ` Andrii Nakryiko
2019-11-13 20:38 ` Daniel Borkmann
2019-11-13 20:50 ` Andrii Nakryiko
2019-11-13 21:10 ` Daniel Borkmann
2019-11-13 21:14 ` Andrii Nakryiko
2019-11-13 3:15 ` [PATCH v3 bpf-next 2/3] libbpf: make global data internal arrays mmap()-able, if possible Andrii Nakryiko
2019-11-13 20:21 ` John Fastabend [this message]
2019-11-13 3:15 ` [PATCH v3 bpf-next 3/3] selftests/bpf: add BPF_TYPE_MAP_ARRAY mmap() tests Andrii Nakryiko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5dcc65d33bdfa_14082b1d9b77e5b4eb@john-XPS-13-9370.notmuch \
--to=john.fastabend@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox