[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190206.165650.1086009975709682209.davem@davemloft.net>
Date: Wed, 06 Feb 2019 16:56:50 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: daniel@...earbox.net
Cc: ast@...nel.org, netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: pull-request: bpf-next 2019-02-07
From: Daniel Borkmann <daniel@...earbox.net>
Date: Thu, 7 Feb 2019 01:42:30 +0100
> The following pull-request contains BPF updates for your *net-next* tree.
>
> The main changes are:
>
> 1) Add a riscv64 JIT for BPF, from Björn.
Awesome.
> 2) Implement BTF deduplication algorithm for libbpf which takes BTF type
> information containing duplicate per-compilation unit information and
> reduces it to an equivalent set of BTF types with no duplication and
> without loss of information, from Andrii.
>
> 3) Offloaded and native BPF XDP programs can coexist today, enable also
> offloaded and generic ones as well, from Jakub.
>
> 4) Expose various BTF related helper functions in libbpf as API which
> are in particular helpful for JITed programs, from Yonghong.
>
> 5) Fix the recently added JMP32 code emission in s390x JIT, from Heiko.
>
> 6) Fix BPF kselftests' tcp_{server,client}.py to be able to run inside
> a network namespace, also add a fix for libbpf to get libbpf_print()
> working, from Stanislav.
>
> 7) Fixes for bpftool documentation, from Prashant.
>
> 8) Type cleanup in BPF kselftests' test_maps.c to silence a gcc8 warning,
> from Breno.
>
> Please consider pulling these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
Pulled, thanks Daniel.
I'll push this back out after my build tests complete.
Powered by blists - more mailing lists