From: Lorenzo Bianconi <lorenzo@kernel.org>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
davem@davemloft.net, kuba@kernel.org, hawk@kernel.org,
john.fastabend@gmail.com, edumazet@google.com, pabeni@redhat.com,
lorenzo.bianconi@redhat.com, toke@toke.dk,
aleksander.lobakin@intel.com, sdf@google.com, tariqt@nvidia.com,
saeedm@nvidia.com, anthony.l.nguyen@intel.com,
przemyslaw.kitszel@intel.com, intel-wired-lan@lists.osuosl.org,
mst@redhat.com, jasowang@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com
Subject: [RFC bpf-next 0/4] Add XDP rx hw hints support performing XDP_REDIRECT
Date: Sat, 21 Sep 2024 18:52:56 +0200 [thread overview]
Message-ID: <cover.1726935917.git.lorenzo@kernel.org> (raw)
This series introduces the xdp_rx_meta struct in the xdp_buff/xdp_frame
one as a container to store the already supported xdp rx hw hints (rx_hash
and rx_vlan, rx_timestamp will be stored in skb_shared_info area) when the
eBPF program running on the nic performs XDP_REDIRECT. Doing so, we are able
to set the skb metadata converting the xdp_buff/xdp_frame to a skb.
Update xdp_metadata_ops callbacks for the following drivers:
- ice
- igc
- mlx5
- mlx4
- veth
- virtio_net
- stmmac
Lorenzo Bianconi (4):
net: xdp: Add xdp_rx_meta structure
net: xdp: Update rx_hash of xdp_rx_meta struct running xmo_rx_hash
callback
net: xdp: Update rx_vlan of xdp_rx_meta struct running xmo_rx_vlan_tag
callback
net: xdp: Update rx timestamp of xdp_rx_meta struct running
xmo_rx_timestamp callback
drivers/net/ethernet/intel/ice/ice_txrx_lib.c | 9 +++
drivers/net/ethernet/intel/igc/igc_main.c | 5 ++
drivers/net/ethernet/mellanox/mlx4/en_rx.c | 3 +
.../net/ethernet/mellanox/mlx5/core/en/xdp.c | 8 ++
.../net/ethernet/stmicro/stmmac/stmmac_main.c | 3 +
drivers/net/veth.c | 9 +++
drivers/net/virtio_net.c | 3 +-
include/net/xdp.h | 79 +++++++++++++++++++
net/core/xdp.c | 29 ++++++-
9 files changed, 146 insertions(+), 2 deletions(-)
--
2.46.1
WARNING: multiple messages have this Message-ID (diff)
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: bpf@vger.kernel.org
Cc: toke@toke.dk, mst@redhat.com, jasowang@redhat.com,
ast@kernel.org, edumazet@google.com, anthony.l.nguyen@intel.com,
sdf@google.com, daniel@iogearbox.net,
przemyslaw.kitszel@intel.com, john.fastabend@gmail.com,
intel-wired-lan@lists.osuosl.org, kuba@kernel.org,
pabeni@redhat.com, hawk@kernel.org, alexandre.torgue@foss.st.com,
netdev@vger.kernel.org, tariqt@nvidia.com,
aleksander.lobakin@intel.com, mcoquelin.stm32@gmail.com,
saeedm@nvidia.com, davem@davemloft.net
Subject: [Intel-wired-lan] [RFC bpf-next 0/4] Add XDP rx hw hints support performing XDP_REDIRECT
Date: Sat, 21 Sep 2024 18:52:56 +0200 [thread overview]
Message-ID: <cover.1726935917.git.lorenzo@kernel.org> (raw)
This series introduces the xdp_rx_meta struct in the xdp_buff/xdp_frame
one as a container to store the already supported xdp rx hw hints (rx_hash
and rx_vlan, rx_timestamp will be stored in skb_shared_info area) when the
eBPF program running on the nic performs XDP_REDIRECT. Doing so, we are able
to set the skb metadata converting the xdp_buff/xdp_frame to a skb.
Update xdp_metadata_ops callbacks for the following drivers:
- ice
- igc
- mlx5
- mlx4
- veth
- virtio_net
- stmmac
Lorenzo Bianconi (4):
net: xdp: Add xdp_rx_meta structure
net: xdp: Update rx_hash of xdp_rx_meta struct running xmo_rx_hash
callback
net: xdp: Update rx_vlan of xdp_rx_meta struct running xmo_rx_vlan_tag
callback
net: xdp: Update rx timestamp of xdp_rx_meta struct running
xmo_rx_timestamp callback
drivers/net/ethernet/intel/ice/ice_txrx_lib.c | 9 +++
drivers/net/ethernet/intel/igc/igc_main.c | 5 ++
drivers/net/ethernet/mellanox/mlx4/en_rx.c | 3 +
.../net/ethernet/mellanox/mlx5/core/en/xdp.c | 8 ++
.../net/ethernet/stmicro/stmmac/stmmac_main.c | 3 +
drivers/net/veth.c | 9 +++
drivers/net/virtio_net.c | 3 +-
include/net/xdp.h | 79 +++++++++++++++++++
net/core/xdp.c | 29 ++++++-
9 files changed, 146 insertions(+), 2 deletions(-)
--
2.46.1
next reply other threads:[~2024-09-21 16:53 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 16:52 Lorenzo Bianconi [this message]
2024-09-21 16:52 ` [Intel-wired-lan] [RFC bpf-next 0/4] Add XDP rx hw hints support performing XDP_REDIRECT Lorenzo Bianconi
2024-09-21 16:52 ` [RFC bpf-next 1/4] net: xdp: Add xdp_rx_meta structure Lorenzo Bianconi
2024-09-21 16:52 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-09-21 16:52 ` [RFC bpf-next 2/4] net: xdp: Update rx_hash of xdp_rx_meta struct running xmo_rx_hash callback Lorenzo Bianconi
2024-09-21 16:52 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-09-21 16:52 ` [RFC bpf-next 3/4] net: xdp: Update rx_vlan of xdp_rx_meta struct running xmo_rx_vlan_tag callback Lorenzo Bianconi
2024-09-21 16:52 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-09-21 16:53 ` [RFC bpf-next 4/4] net: xdp: Update rx timestamp of xdp_rx_meta struct running xmo_rx_timestamp callback Lorenzo Bianconi
2024-09-21 16:53 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-09-21 20:17 ` [RFC bpf-next 0/4] Add XDP rx hw hints support performing XDP_REDIRECT Alexander Lobakin
2024-09-21 20:17 ` [Intel-wired-lan] " Alexander Lobakin
2024-09-21 21:36 ` Jesper Dangaard Brouer
2024-09-21 21:36 ` [Intel-wired-lan] " Jesper Dangaard Brouer
2024-09-22 9:17 ` Lorenzo Bianconi
2024-09-22 9:17 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-09-22 11:12 ` Toke Høiland-Jørgensen
2024-09-22 11:12 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-09-22 15:40 ` Lorenzo Bianconi
2024-09-22 15:40 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-09-26 10:54 ` Toke Høiland-Jørgensen
2024-09-26 10:54 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-09-26 14:57 ` Lorenzo Bianconi
2024-09-26 14:57 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-09-27 1:43 ` Stanislav Fomichev
2024-09-27 1:43 ` [Intel-wired-lan] " Stanislav Fomichev
2024-09-26 11:31 ` Arthur Fabre
2024-09-26 11:31 ` [Intel-wired-lan] " Arthur Fabre
2024-09-26 12:41 ` Toke Høiland-Jørgensen
2024-09-26 12:41 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-09-26 15:44 ` Arthur Fabre
2024-09-26 15:44 ` [Intel-wired-lan] " Arthur Fabre
2024-09-27 10:24 ` Toke Høiland-Jørgensen
2024-09-27 10:24 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-09-27 14:46 ` Arthur Fabre
2024-09-27 14:46 ` [Intel-wired-lan] " Arthur Fabre
2024-09-27 15:06 ` Lorenzo Bianconi
2024-09-27 15:06 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-09-30 10:58 ` Toke Høiland-Jørgensen
2024-09-30 10:58 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-09-30 11:49 ` Lorenzo Bianconi
2024-09-30 11:49 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-10-01 14:16 ` Arthur Fabre
2024-10-01 14:16 ` [Intel-wired-lan] " Arthur Fabre
2024-10-01 14:54 ` Lorenzo Bianconi
2024-10-01 14:54 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-10-01 15:14 ` Toke Høiland-Jørgensen
2024-10-01 15:14 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-10-02 17:02 ` Stanislav Fomichev
2024-10-02 17:02 ` [Intel-wired-lan] " Stanislav Fomichev
2024-10-02 18:38 ` Toke Høiland-Jørgensen
2024-10-02 18:38 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-10-02 22:49 ` Stanislav Fomichev
2024-10-02 22:49 ` [Intel-wired-lan] " Stanislav Fomichev
2024-10-03 6:35 ` Arthur Fabre
2024-10-03 6:35 ` [Intel-wired-lan] " Arthur Fabre
2024-10-03 20:26 ` Stanislav Fomichev
2024-10-03 20:26 ` [Intel-wired-lan] " Stanislav Fomichev
2024-10-04 2:13 ` Daniel Xu
2024-10-04 2:13 ` [Intel-wired-lan] " Daniel Xu
2024-10-04 10:38 ` Jesper Dangaard Brouer
2024-10-04 10:38 ` [Intel-wired-lan] " Jesper Dangaard Brouer
2024-10-04 13:55 ` Arthur Fabre
2024-10-04 13:55 ` [Intel-wired-lan] " Arthur Fabre
2024-10-04 14:14 ` Jesper Dangaard Brouer
2024-10-04 14:14 ` [Intel-wired-lan] " Jesper Dangaard Brouer
2024-10-04 14:18 ` Lorenzo Bianconi
2024-10-04 14:18 ` [Intel-wired-lan] " Lorenzo Bianconi
2024-10-04 14:29 ` Arthur Fabre
2024-10-04 14:29 ` [Intel-wired-lan] " Arthur Fabre
2024-10-04 17:53 ` Stanislav Fomichev
2024-10-04 17:53 ` [Intel-wired-lan] " Stanislav Fomichev
2024-10-06 10:27 ` Toke Høiland-Jørgensen
2024-10-06 10:27 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-10-07 18:48 ` Stanislav Fomichev
2024-10-07 18:48 ` [Intel-wired-lan] " Stanislav Fomichev
2024-10-08 7:15 ` Arthur Fabre
2024-10-08 7:15 ` [Intel-wired-lan] " Arthur Fabre
2024-10-04 16:27 ` Stanislav Fomichev
2024-10-04 16:27 ` [Intel-wired-lan] " Stanislav Fomichev
2024-09-30 10:52 ` Toke Høiland-Jørgensen
2024-09-30 10:52 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-10-01 14:06 ` Arthur Fabre
2024-10-01 14:06 ` [Intel-wired-lan] " Arthur Fabre
2024-10-01 15:28 ` Toke Høiland-Jørgensen
2024-10-01 15:28 ` [Intel-wired-lan] " Toke Høiland-Jørgensen
2024-10-03 6:51 ` Arthur Fabre
2024-10-03 6:51 ` [Intel-wired-lan] " Arthur Fabre
2024-09-22 9:08 ` Lorenzo Bianconi
2024-09-22 9:08 ` [Intel-wired-lan] " Lorenzo Bianconi
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=cover.1726935917.git.lorenzo@kernel.org \
--to=lorenzo@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=saeedm@nvidia.com \
--cc=sdf@google.com \
--cc=tariqt@nvidia.com \
--cc=toke@toke.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.