From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Claudiu Manoil" <claudiu.manoil@nxp.com>,
"Björn Töpel" <bjorn@kernel.org>,
"Magnus Karlsson" <magnus.karlsson@intel.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next 00/11] NXP ENETC AF_XDP zero-copy sockets
Date: Wed, 8 Feb 2023 17:41:59 +0100 [thread overview]
Message-ID: <Y+PQ1+j0l/h/6dx+@boxer> (raw)
In-Reply-To: <20230206100837.451300-1-vladimir.oltean@nxp.com>
On Mon, Feb 06, 2023 at 12:08:26PM +0200, Vladimir Oltean wrote:
> This is RFC because I have a few things I'm not 100% certain about.
> I've tested this with the xdpsock test application, I don't have very
> detailed knowledge about the internals of AF_XDP sockets.
>
> Patches where I'd appreciate if people took a look are 02/11, 05/11,
> 10/11 and 11/11.
All of that looks rather sane to me. Can you point out explicitly your
issues here? Is it around concurrent access to XDP Tx rings or something
more?
I commented on 10 and 11. For 2 it seems fine and 5 has always been
controversial.
>
> Vladimir Oltean (11):
> net: enetc: optimize struct enetc_rx_swbd layout
> net: enetc: perform XDP RX queue registration at enetc_setup_bpf()
> time
> net: enetc: rename "cleaned_cnt" to "buffs_missing"
> net: enetc: continue NAPI processing on frames with RX errors
> net: enetc: add support for ethtool --show-channels
> net: enetc: consolidate rx_swbd freeing
> net: enetc: rename enetc_free_tx_frame() to enetc_free_tx_swbd()
> net: enetc: increment rx_byte_cnt for XDP data path
> net: enetc: move setting of ENETC_TXBD_FLAGS_F flag to
> enetc_xdp_map_tx_buff()
> net: enetc: add RX support for zero-copy XDP sockets
> net: enetc: add TX support for zero-copy XDP sockets
>
> drivers/net/ethernet/freescale/enetc/enetc.c | 676 +++++++++++++++---
> drivers/net/ethernet/freescale/enetc/enetc.h | 9 +-
> .../ethernet/freescale/enetc/enetc_ethtool.c | 10 +
> .../net/ethernet/freescale/enetc/enetc_pf.c | 1 +
> 4 files changed, 606 insertions(+), 90 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2023-02-08 16:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 10:08 [RFC PATCH net-next 00/11] NXP ENETC AF_XDP zero-copy sockets Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 01/11] net: enetc: optimize struct enetc_rx_swbd layout Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 02/11] net: enetc: perform XDP RX queue registration at enetc_setup_bpf() time Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 03/11] net: enetc: rename "cleaned_cnt" to "buffs_missing" Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 04/11] net: enetc: continue NAPI processing on frames with RX errors Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 05/11] net: enetc: add support for ethtool --show-channels Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 06/11] net: enetc: consolidate rx_swbd freeing Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 07/11] net: enetc: rename enetc_free_tx_frame() to enetc_free_tx_swbd() Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 08/11] net: enetc: increment rx_byte_cnt for XDP data path Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 09/11] net: enetc: move setting of ENETC_TXBD_FLAGS_F flag to enetc_xdp_map_tx_buff() Vladimir Oltean
2023-02-06 10:08 ` [RFC PATCH net-next 10/11] net: enetc: add RX support for zero-copy XDP sockets Vladimir Oltean
2023-02-08 16:36 ` Maciej Fijalkowski
2023-02-06 10:08 ` [RFC PATCH net-next 11/11] net: enetc: add TX " Vladimir Oltean
2023-02-06 10:19 ` Vladimir Oltean
2023-02-08 16:38 ` Maciej Fijalkowski
2023-02-08 16:37 ` Maciej Fijalkowski
2023-02-08 17:08 ` Vladimir Oltean
2023-02-08 17:17 ` Maciej Fijalkowski
2023-03-20 16:30 ` Vladimir Oltean
2023-02-08 16:41 ` Maciej Fijalkowski [this message]
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=Y+PQ1+j0l/h/6dx+@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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).