[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0aa6a69a-0bbe-e0fc-1e18-2114adb18c51@gmail.com>
Date: Sun, 1 Dec 2019 09:54:44 -0700
From: David Ahern <dsahern@...il.com>
To: Jason Wang <jasowang@...hat.com>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc: Song Liu <songliubraving@...com>,
Jesper Dangaard Brouer <hawk@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
"Michael S . Tsirkin" <mst@...hat.com>, qemu-devel@...gnu.org,
netdev@...r.kernel.org, John Fastabend <john.fastabend@...il.com>,
Alexei Starovoitov <ast@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Prashant Bhole <prashantbhole.linux@...il.com>,
kvm@...r.kernel.org, Yonghong Song <yhs@...com>,
Andrii Nakryiko <andriin@...com>,
"David S . Miller" <davem@...emloft.net>
Subject: Re: [RFC net-next 00/18] virtio_net XDP offload
On 11/27/19 10:18 PM, Jason Wang wrote:
> We try to follow what NFP did by starting from a fraction of the whole
> eBPF features. It would be very hard to have all eBPF features
> implemented from the start. It would be helpful to clarify what's the
> minimal set of features that you want to have from the start.
Offloading guest programs needs to prevent a guest XDP program from
running bpf helpers that access host kernel data. e.g., bpf_fib_lookup
Powered by blists - more mailing lists