[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5a028e5a-5207-d02a-ddc7-29a5117e93fc@iogearbox.net>
Date: Mon, 15 Jan 2018 01:00:17 +0100
From: Daniel Borkmann <daniel@...earbox.net>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>,
alexei.starovoitov@...il.com, davem@...emloft.net
Cc: netdev@...r.kernel.org, oss-drivers@...ronome.com, tehnerd@...com
Subject: Re: [PATCH bpf-next v2 00/15] bpf: support creating maps on
networking devices
On 01/12/2018 05:29 AM, Jakub Kicinski wrote:
> Hi!
>
> This set adds support for creating maps on networking devices. BPF is
> programs+maps, the pure program offload has been around for quite some
> time, this patchset adds the map part of the equation.
>
> Maps are allocated on the target device from the start. There is no
> host copy when map is created on the device. Device maps are represented
> by struct bpf_offloaded_map, regardless of type. Host programs can't
> access such maps, access is only possible from a program also loaded
> to the same device and/or via the BPF syscall.
>
> Offloaded programs are currently only allowed to perform lookups,
> control plane is responsible for populating the maps.
>
> For brevity only infrastructure and basic NFP patches are included.
> Target device reporting, netdevsim and tests will follow up as well as
> some further optimizations to the NFP code.
>
> v2:
> - leave out the array maps, we will add them trivially later to avoid
> merge conflicts with ongoing spectere&meltdown mitigations.
Series applied to bpf-next, thanks Jakub!
Powered by blists - more mailing lists