From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: pull-request: bpf-next 2017-12-18 Date: Mon, 18 Dec 2017 10:51:53 -0500 (EST) Message-ID: <20171218.105153.395572657387757515.davem@davemloft.net> References: <20171218003307.10014-1-daniel@iogearbox.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: ast@kernel.org, netdev@vger.kernel.org To: daniel@iogearbox.net Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:36922 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933336AbdLRPvz (ORCPT ); Mon, 18 Dec 2017 10:51:55 -0500 In-Reply-To: <20171218003307.10014-1-daniel@iogearbox.net> Sender: netdev-owner@vger.kernel.org List-ID: From: Daniel Borkmann Date: Mon, 18 Dec 2017 01:33:07 +0100 > The following pull-request contains BPF updates for your *net-next* tree. > > The main changes are: > > 1) Allow arbitrary function calls from one BPF function to another BPF function. > As of today when writing BPF programs, __always_inline had to be used in > the BPF C programs for all functions, unnecessarily causing LLVM to inflate > code size. Handle this more naturally with support for BPF to BPF calls > such that this __always_inline restriction can be overcome. As a result, > it allows for better optimized code and finally enables to introduce core > BPF libraries in the future that can be reused out of different projects. > x86 and arm64 JIT support was added as well, from Alexei. Exciting... but now there's a lot of JIT work to do. ... > Please consider pulling these changes from: > > git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git Pulled, thanks!