From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf <bpf@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Joe Stringer <joe@wand.net.nz>, Yonghong Song <yhs@fb.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Martin KaFai Lau <kafai@fb.com>, Jann Horn <jannh@google.com>
Subject: Re: [PATCH bpf-next v6 00/16] BPF support for global data
Date: Tue, 9 Apr 2019 17:10:33 -0700 [thread overview]
Message-ID: <CAADnVQKaPEi5-vjG_fvt0o8e9b9wAC665++3s48sD2h0qLhoiQ@mail.gmail.com> (raw)
In-Reply-To: <20190409210910.32048-1-daniel@iogearbox.net>
On Tue, Apr 9, 2019 at 2:09 PM Daniel Borkmann <daniel@iogearbox.net> wrote:
>
> This series is a major rework of previously submitted libbpf
> patches [0] in order to add global data support for BPF. The
> kernel has been extended to add proper infrastructure that allows
> for full .bss/.data/.rodata sections on BPF loader side based
> upon feedback from LPC discussions [1]. Latter support is then
> also added into libbpf in this series which allows for more
> natural C-like programming of BPF programs. For more information
> on loader, please refer to 'bpf, libbpf: support global data/bss/
> rodata sections' patch in this series.
>
> Thanks a lot!
>
> v5 -> v6:
> - Removed synchronize_rcu() from map freeze (Jann)
> - Rest as-is
> v4 -> v5:
> - Removed index selection again for ldimm64 (Alexei)
> - Adapted related test cases and added new ones to test
> rejection of off != 0
> v3 -> v4:
> - Various fixes in BTF verification e.g. to disallow
> Var and DataSec to be an intermediate type during resolve (Martin)
> - More BTF test cases added
> - Few cleanups in key-less BTF commit (Martin)
> - Bump libbpf minor version from 2 to 3
> - Renamed and simplified read-only locking
> - Various minor improvements all over the place
> v2 -> v3:
> - Implement BTF support in kernel, libbpf, bpftool, add tests
> - Fix idx + off conversion (Andrii)
> - Document lower / higher bits for direct value access (Andrii)
> - Add tests with small value size (Andrii)
> - Add index selection into ldimm64 (Andrii)
> - Fix missing fdput() (Jann)
> - Reject invalid flags in BPF_F_*_PROG (Jakub)
> - Complete rework of libbpf support, includes:
> - Add objname to map name (Stanislav)
> - Make .rodata map full read-only after setup (Andrii)
> - Merge relocation handling into single one (Andrii)
> - Store global maps into obj->maps array (Andrii, Alexei)
> - Debug message when skipping section (Andrii)
> - Reject non-static global data till we have
> semantics for sharing them (Yonghong, Andrii, Alexei)
> - More test cases and completely reworked prog test (Alexei)
> - Fixes, cleanups, etc all over the set
> - Not yet addressed:
> - Make BTF mandatory for these maps (Alexei)
> -> Waiting till BTF support for these lands first
> v1 -> v2:
> - Instead of 32-bit static data, implement full global
> data support (Alexei)
>
> [0] https://patchwork.ozlabs.org/cover/1040290/
> [1] http://vger.kernel.org/lpc-bpf2018.html#session-3
Applied to bpf-next. Thanks!
next prev parent reply other threads:[~2019-04-10 0:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 21:08 [PATCH bpf-next v6 00/16] BPF support for global data Daniel Borkmann
2019-04-09 21:08 ` [PATCH bpf-next v6 01/16] bpf: implement lookup-free direct value access for maps Daniel Borkmann
2019-04-09 21:08 ` [PATCH bpf-next v6 02/16] bpf: do not retain flags that are not tied to map lifetime Daniel Borkmann
2019-04-09 21:08 ` [PATCH bpf-next v6 03/16] bpf: add program side {rd, wr}only support for maps Daniel Borkmann
2019-04-09 21:08 ` [PATCH bpf-next v6 04/16] bpf: add syscall side map freeze support Daniel Borkmann
2019-04-09 21:08 ` [PATCH bpf-next v6 05/16] bpf: allow . char as part of the object name Daniel Borkmann
2019-04-09 21:09 ` [PATCH bpf-next v6 06/16] bpf: add specification for BTF Var and DataSec kinds Daniel Borkmann
2019-04-09 21:09 ` [PATCH bpf-next v6 07/16] bpf: kernel side support for BTF Var and DataSec Daniel Borkmann
2019-04-10 0:10 ` Alexei Starovoitov [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-09 21:20 [PATCH bpf-next v6 00/16] BPF support for global data Daniel Borkmann
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=CAADnVQKaPEi5-vjG_fvt0o8e9b9wAC665++3s48sD2h0qLhoiQ@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jannh@google.com \
--cc=joe@wand.net.nz \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=yhs@fb.com \
/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;
as well as URLs for NNTP newsgroup(s).