From: Ahmed Zaki <ahmed.zaki@intel.com>
To: netdev@vger.kernel.org
Cc: intel-wired-lan@lists.osuosl.org, linux-doc@vger.kernel.org,
corbet@lwn.net, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
vladimir.oltean@nxp.com, andrew@lunn.ch, horms@kernel.org,
mkubecek@suse.cz, Ahmed Zaki <ahmed.zaki@intel.com>
Subject: [PATCH net-next v2 0/6] Support symmetric RSS (Toeplitz) hash
Date: Fri, 6 Oct 2023 16:47:20 -0600 [thread overview]
Message-ID: <20231006224726.443836-1-ahmed.zaki@intel.com> (raw)
Patch 1 adds the support at the Kernel level, allowing the user to set a
symmetric RSS hash for any flow type via:
# ethtool -N|-U eth0 rx-flow-hash <flow_type> s|d|f|n symmetric
Support for the new "symmetric" flag will be later sent to the "ethtool"
user-space tool.
Patch 2 fixes a long standing bug with the register values. The bug has
been benign for now since only symmetric Toeplitz hash (Zero) has been
used.
Patches 3 and 4 lay some groundwork refactoring. While the first is
mainly cosmetic, the second is needed since there is no more room in the
previous 64-bit RSS profile ID for the symmetric attribute introduced in
the next patch.
Finally, patches 5 and 6 add the symmetric Toeplitz support for the ice
(E800 PFs) and the iAVF drivers.
---
v2: fixed a "Reviewed by" to "Reviewed-by", also need to cc maintainers.
Ahmed Zaki (4):
net: ethtool: allow symmetric RSS hash for any flow type
ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values
ice: refactor the FD and RSS flow ID generation
iavf: enable symmetric RSS Toeplitz hash
Jeff Guo (1):
ice: enable symmetric RSS Toeplitz hash for any flow type
Qi Zhang (1):
ice: refactor RSS configuration
Documentation/networking/scaling.rst | 6 +
.../net/ethernet/intel/iavf/iavf_adv_rss.c | 8 +-
.../net/ethernet/intel/iavf/iavf_adv_rss.h | 3 +-
.../net/ethernet/intel/iavf/iavf_ethtool.c | 22 +-
drivers/net/ethernet/intel/ice/ice.h | 2 +
.../net/ethernet/intel/ice/ice_adminq_cmd.h | 8 +-
drivers/net/ethernet/intel/ice/ice_common.h | 1 +
drivers/net/ethernet/intel/ice/ice_ethtool.c | 14 +-
.../net/ethernet/intel/ice/ice_ethtool_fdir.c | 35 +-
.../net/ethernet/intel/ice/ice_flex_pipe.c | 43 +-
.../net/ethernet/intel/ice/ice_flex_pipe.h | 4 +-
.../net/ethernet/intel/ice/ice_flex_type.h | 7 +
drivers/net/ethernet/intel/ice/ice_flow.c | 439 +++++++++++++-----
drivers/net/ethernet/intel/ice/ice_flow.h | 46 +-
.../net/ethernet/intel/ice/ice_hw_autogen.h | 4 +
drivers/net/ethernet/intel/ice/ice_lib.c | 117 ++---
drivers/net/ethernet/intel/ice/ice_main.c | 49 +-
drivers/net/ethernet/intel/ice/ice_type.h | 1 +
drivers/net/ethernet/intel/ice/ice_virtchnl.c | 55 ++-
.../ethernet/intel/ice/ice_virtchnl_fdir.c | 35 +-
include/linux/avf/virtchnl.h | 16 +-
include/uapi/linux/ethtool.h | 1 +
net/ethtool/ioctl.c | 11 +
23 files changed, 629 insertions(+), 298 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-06 22:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 22:47 Ahmed Zaki [this message]
2023-10-06 22:47 ` [PATCH net-next v2 1/6] net: ethtool: allow symmetric RSS hash for any flow type Ahmed Zaki
2023-10-07 0:22 ` Jakub Kicinski
2023-10-07 9:01 ` Willem de Bruijn
2023-10-10 20:10 ` Ahmed Zaki
2023-10-06 22:47 ` [PATCH net-next v2 2/6] ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values Ahmed Zaki
2023-10-09 16:37 ` Jakub Kicinski
2023-10-10 20:08 ` Ahmed Zaki
2023-10-06 22:47 ` [PATCH net-next v2 3/6] ice: refactor RSS configuration Ahmed Zaki
2023-10-06 22:47 ` [PATCH net-next v2 4/6] ice: refactor the FD and RSS flow ID generation Ahmed Zaki
2023-10-06 22:47 ` [PATCH net-next v2 5/6] ice: enable symmetric RSS Toeplitz hash for any flow type Ahmed Zaki
2023-10-06 22:47 ` [PATCH net-next v2 6/6] iavf: enable symmetric RSS Toeplitz hash Ahmed Zaki
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=20231006224726.443836-1-ahmed.zaki@intel.com \
--to=ahmed.zaki@intel.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=mkubecek@suse.cz \
--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).