From: Jesper Dangaard Brouer <brouer@redhat.com>
To: bpf@vger.kernel.org
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
netdev@vger.kernel.org, Stanislav Fomichev <sdf@google.com>,
martin.lau@kernel.org, ast@kernel.org, daniel@iogearbox.net,
alexandr.lobakin@intel.com, larysa.zaremba@intel.com,
xdp-hints@xdp-project.net, anthony.l.nguyen@intel.com,
yoong.siang.song@intel.com, boon.leong.ong@intel.com,
intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
jesse.brandeburg@intel.com, kuba@kernel.org, edumazet@google.com,
john.fastabend@gmail.com, hawk@kernel.org, davem@davemloft.net
Subject: [xdp-hints] [PATCH bpf RFC 0/4] XDP-hints: API change for RX-hash kfunc bpf_xdp_metadata_rx_hash
Date: Tue, 28 Mar 2023 22:15:53 +0200 [thread overview]
Message-ID: <168003451121.3027256.13000250073816770554.stgit@firesoul> (raw)
Notice targeted 6.3-rc kernel via bpf git tree.
Current API for bpf_xdp_metadata_rx_hash() returns the raw RSS hash value,
but doesn't provide information on the RSS hash type (part of 6.3-rc).
This patchset proposal is to use the return value from
bpf_xdp_metadata_rx_hash() to provide the RSS hash type.
---
Jesper Dangaard Brouer (4):
xdp: rss hash types representation
igc: bpf_xdp_metadata_rx_hash return xdp rss hash type
veth: bpf_xdp_metadata_rx_hash return xdp rss hash type
mlx5: bpf_xdp_metadata_rx_hash return xdp rss hash type
drivers/net/ethernet/intel/igc/igc_main.c | 22 ++++++-
.../net/ethernet/mellanox/mlx5/core/en/xdp.c | 61 ++++++++++++++++++-
drivers/net/veth.c | 2 +-
include/linux/mlx5/device.h | 14 ++++-
include/net/xdp.h | 54 ++++++++++++++++
net/core/xdp.c | 4 +-
6 files changed, 150 insertions(+), 7 deletions(-)
--
next reply other threads:[~2023-03-28 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 20:15 Jesper Dangaard Brouer [this message]
2023-03-28 20:15 ` [xdp-hints] [PATCH bpf RFC 1/4] xdp: rss hash types representation Jesper Dangaard Brouer
2023-03-28 21:58 ` [xdp-hints] " Stanislav Fomichev
2023-03-29 11:23 ` Jesper Dangaard Brouer
2023-03-29 17:18 ` Stanislav Fomichev
2023-03-29 18:19 ` Jesper Dangaard Brouer
2023-03-29 23:19 ` Stanislav Fomichev
2023-03-30 9:51 ` Jesper Dangaard Brouer
2023-03-30 17:11 ` Stanislav Fomichev
2023-03-30 18:52 ` Jesper Dangaard Brouer
2023-03-29 8:10 ` Edward Cree
2023-03-29 12:13 ` Jesper Dangaard Brouer
2023-03-28 20:16 ` [xdp-hints] [PATCH bpf RFC 2/4] igc: bpf_xdp_metadata_rx_hash return xdp rss hash type Jesper Dangaard Brouer
2023-03-28 20:16 ` [xdp-hints] [PATCH bpf RFC 3/4] veth: " Jesper Dangaard Brouer
2023-03-28 20:16 ` [xdp-hints] [PATCH bpf RFC 4/4] mlx5: " 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
List information: https://lists.xdp-project.net/postorius/lists/xdp-hints.xdp-project.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=168003451121.3027256.13000250073816770554.stgit@firesoul \
--to=brouer@redhat.com \
--cc=alexandr.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=boon.leong.ong@intel.com \
--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=jesse.brandeburg@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=xdp-hints@xdp-project.net \
--cc=yoong.siang.song@intel.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