From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: 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, alexei.starovoitov@gmail.com,
tariqt@mellanox.com, brouer@redhat.com
Subject: Re: [net-next V9 PATCH 00/16] XDP redirect memory return API
Date: Tue, 3 Apr 2018 18:07:16 +0200 [thread overview]
Message-ID: <20180403180716.66c3daee@redhat.com> (raw)
In-Reply-To: <20180403.105427.1908874085989267860.davem@davemloft.net>
On Tue, 03 Apr 2018 10:54:27 -0400 (EDT)
David Miller <davem@davemloft.net> wrote:
> From: Jesper Dangaard Brouer <brouer@redhat.com>
> Date: Tue, 03 Apr 2018 13:07:36 +0200
>
> > This is V9, but it's worth mentioning that V8 was send against
> > net-next, because i40e got XDP_REDIRECT support in-between V6, and it
> > doesn't exist in bpf-next yet. Most significant change in V8 was that
> > page_pool only gets compiled into the kernel when a drivers Kconfig
> > 'select' the feature.
>
> Jesper, this series now looks good to me, however the net-next tree is
> closed at this point.
I noticed, but though that in-flight patchset's were still allowed...
> Don't worry, just resubmit when net-next opens back up.
At that point in time, should I got back to posting it against the
bpf-next git-tree again? Any preferences from Mellanox or BPF-guys?
... It have been a bit of a pain to keep track of driver changes in
net-next, and waiting for them to get merged into bpf-next.
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2018-04-03 16:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 11:07 [net-next V9 PATCH 00/16] XDP redirect memory return API Jesper Dangaard Brouer
2018-04-03 11:07 ` [net-next V9 PATCH 01/16] mlx5: basic XDP_REDIRECT forward support Jesper Dangaard Brouer
2018-04-03 11:07 ` [net-next V9 PATCH 02/16] xdp: introduce xdp_return_frame API and use in cpumap Jesper Dangaard Brouer
2018-04-03 11:07 ` [net-next V9 PATCH 03/16] ixgbe: use xdp_return_frame API Jesper Dangaard Brouer
2018-04-03 11:07 ` [net-next V9 PATCH 04/16] xdp: move struct xdp_buff from filter.h to xdp.h Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 05/16] xdp: introduce a new xdp_frame type Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 06/16] tun: convert to use generic xdp_frame and xdp_return_frame API Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 07/16] virtio_net: " Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 08/16] bpf: cpumap convert to use generic xdp_frame Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 09/16] i40e: convert to use generic xdp_frame and xdp_return_frame API Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 10/16] mlx5: register a memory model when XDP is enabled Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 11/16] xdp: rhashtable with allocator ID to pointer mapping Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 12/16] page_pool: refurbish version of page_pool code Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 13/16] xdp: allow page_pool as an allocator type in xdp_return_frame Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 14/16] mlx5: use page_pool for xdp_return_frame call Jesper Dangaard Brouer
2018-04-04 13:12 ` Tariq Toukan
2018-04-04 13:36 ` Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 15/16] xdp: transition into using xdp_frame for return API Jesper Dangaard Brouer
2018-04-03 11:08 ` [net-next V9 PATCH 16/16] xdp: transition into using xdp_frame for ndo_xdp_xmit Jesper Dangaard Brouer
2018-04-03 14:54 ` [net-next V9 PATCH 00/16] XDP redirect memory return API David Miller
2018-04-03 16:07 ` Jesper Dangaard Brouer [this message]
2018-04-03 16:23 ` David Miller
2018-04-03 17:03 ` Saeed Mahameed
2018-04-04 8:41 ` Daniel Borkmann
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=20180403180716.66c3daee@redhat.com \
--to=brouer@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=borkmann@iogearbox.net \
--cc=davem@davemloft.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;
as well as URLs for NNTP newsgroup(s).