From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: alexei.starovoitov@gmail.com, brouer@redhat.com,
netdev@vger.kernel.org, bjorn.topel@intel.com,
magnus.karlsson@intel.com, eugenia@mellanox.com,
jasowang@redhat.com, john.fastabend@gmail.com,
eranbe@mellanox.com, saeedm@mellanox.com, galp@mellanox.com,
borkmann@iogearbox.net, tariqt@mellanox.com
Subject: Re: [net-next V11 PATCH 00/17] XDP redirect memory return API
Date: Tue, 17 Apr 2018 11:35:48 -0400 (EDT) [thread overview]
Message-ID: <20180417.113548.676760038759107548.davem@davemloft.net> (raw)
In-Reply-To: <89dee120-76a4-f7dd-82ec-1d8a9fcb29d8@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Tue, 17 Apr 2018 17:24:03 +0200
> On 04/17/2018 05:18 PM, David Miller wrote:
>> From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
>> Date: Tue, 17 Apr 2018 07:48:42 -0700
>>
>>> On Tue, Apr 17, 2018 at 04:45:16PM +0200, Jesper Dangaard Brouer wrote:
>>>> Submitted 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 series look good to me now.
>>> Acked-by: Alexei Starovoitov <ast@kernel.org>
>>
>> Pushed out to net-next, thanks everyone!
>
> See my comment on the last patch which is actually buggy. But given it's
> pushed out already, then it needs to be fixed as follow-up..
Yes it will need to be dealt with as a follow-up.
next prev parent reply other threads:[~2018-04-17 15:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 14:45 [net-next V11 PATCH 00/17] XDP redirect memory return API Jesper Dangaard Brouer
2018-04-17 14:45 ` [net-next V11 PATCH 01/17] mlx5: basic XDP_REDIRECT forward support Jesper Dangaard Brouer
2018-04-17 14:45 ` [net-next V11 PATCH 02/17] xdp: introduce xdp_return_frame API and use in cpumap Jesper Dangaard Brouer
2018-04-17 14:45 ` [net-next V11 PATCH 03/17] ixgbe: use xdp_return_frame API Jesper Dangaard Brouer
2018-04-17 14:45 ` [net-next V11 PATCH 04/17] xdp: move struct xdp_buff from filter.h to xdp.h Jesper Dangaard Brouer
2018-04-17 14:45 ` [net-next V11 PATCH 05/17] xdp: introduce a new xdp_frame type Jesper Dangaard Brouer
2018-04-17 14:45 ` [net-next V11 PATCH 06/17] tun: convert to use generic xdp_frame and xdp_return_frame API Jesper Dangaard Brouer
2018-04-17 14:45 ` [net-next V11 PATCH 07/17] virtio_net: " Jesper Dangaard Brouer
2018-04-17 14:45 ` [net-next V11 PATCH 08/17] bpf: cpumap convert to use generic xdp_frame Jesper Dangaard Brouer
2018-04-17 14:46 ` [net-next V11 PATCH 09/17] i40e: convert to use generic xdp_frame and xdp_return_frame API Jesper Dangaard Brouer
2018-04-17 14:46 ` [net-next V11 PATCH 10/17] mlx5: register a memory model when XDP is enabled Jesper Dangaard Brouer
2018-04-17 14:46 ` [net-next V11 PATCH 11/17] xdp: rhashtable with allocator ID to pointer mapping Jesper Dangaard Brouer
2018-04-17 14:46 ` [net-next V11 PATCH 12/17] page_pool: refurbish version of page_pool code Jesper Dangaard Brouer
2018-04-17 14:46 ` [net-next V11 PATCH 13/17] xdp: allow page_pool as an allocator type in xdp_return_frame Jesper Dangaard Brouer
2018-04-17 14:46 ` [net-next V11 PATCH 14/17] mlx5: use page_pool for xdp_return_frame call Jesper Dangaard Brouer
2018-04-17 14:46 ` [net-next V11 PATCH 15/17] xdp: transition into using xdp_frame for return API Jesper Dangaard Brouer
2018-04-17 14:46 ` [net-next V11 PATCH 16/17] xdp: transition into using xdp_frame for ndo_xdp_xmit Jesper Dangaard Brouer
2018-04-17 14:46 ` [net-next V11 PATCH 17/17] xdp: avoid leaking info stored in frame data on page reuse Jesper Dangaard Brouer
2018-04-17 15:04 ` Daniel Borkmann
2018-04-17 14:48 ` [net-next V11 PATCH 00/17] XDP redirect memory return API Alexei Starovoitov
2018-04-17 15:18 ` David Miller
2018-04-17 15:24 ` Daniel Borkmann
2018-04-17 15:35 ` David Miller [this message]
2018-04-17 16:27 ` Jesper Dangaard Brouer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180417.113548.676760038759107548.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=borkmann@iogearbox.net \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=eranbe@mellanox.com \
--cc=eugenia@mellanox.com \
--cc=galp@mellanox.com \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox