Re: [net-next V10 PATCH 00/16] XDP redirect memory return API

On Tue, 17 Apr 2018 10:07:50 -0400 (EDT) David Miller wrote: > From: Alexei Starovoitov > Date: Tue, 17 Apr 2018 06:53:33 -0700 > > > looks like you forgot to include extra patch to fixup xdp_adjust_head() > > helper. Otherwise reused

Re: [net-next V10 PATCH 00/16] XDP redirect memory return API

From: Alexei Starovoitov Date: Tue, 17 Apr 2018 06:53:33 -0700 > looks like you forgot to include extra patch to fixup xdp_adjust_head() > helper. Otherwise reused xdp_frame in the top of that packet is leaking > kernel pointers into bpf program. > Could you please

Re: [net-next V10 PATCH 00/16] XDP redirect memory return API

From: Jesper Dangaard Brouer Date: Tue, 17 Apr 2018 14:58:52 +0200 > Resubmit V10 against net-next, as it contains NIC driver changes. Series applied, thanks Jesper.

Re: [net-next V10 PATCH 00/16] XDP redirect memory return API

On Tue, Apr 17, 2018 at 5:58 AM, Jesper Dangaard Brouer wrote: > Resubmit V10 against net-next, as it contains NIC driver changes. > > This patchset works towards supporting different XDP RX-ring memory > allocators. As this will be needed by the AF_XDP zero-copy mode. > > The

[net-next V10 PATCH 00/16] XDP redirect memory return API

Resubmit V10 against net-next, as it contains NIC driver changes. This patchset works towards supporting different XDP RX-ring memory allocators. As this will be needed by the AF_XDP zero-copy mode. The patchset uses mlx5 as the sample driver, which gets implemented XDP_REDIRECT RX-mode, but