From: patchwork-bot+netdevbpf@kernel.org
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: mkubecek@suse.cz, andrew@lunn.ch,
willemdebruijn.kernel@gmail.com, corbet@lwn.net,
netdev@vger.kernel.org, gal@nvidia.com,
linux-doc@vger.kernel.org, jesse.brandeburg@intel.com,
vladimir.oltean@nxp.com, ecree.xilinx@gmail.com,
edumazet@google.com, anthony.l.nguyen@intel.com,
horms@kernel.org, kuba@kernel.org,
intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next v9 0/8] Support symmetric-xor RSS hash
Date: Thu, 14 Dec 2023 06:20:27 +0000 [thread overview]
Message-ID: <170253482778.28524.4770397031071631009.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231213003321.605376-1-ahmed.zaki@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 12 Dec 2023 17:33:13 -0700 you wrote:
> Patches 1 and 2 modify the get/set_rxh ethtool API to take a pointer to
> struct of parameters instead of individual params. This will allow future
> changes to the uAPI-shared struct ethtool_rxfh without changing the
> drivers' API.
>
> Patch 3 adds the support at the Kernel level, allowing the user to set a
> symmetric-xor RSS hash for a netdevice via:
>
> [...]
Here is the summary with links:
- [net-next,v9,1/8] net: ethtool: pass a pointer to parameters to get/set_rxfh ethtool ops
https://git.kernel.org/netdev/net-next/c/fb6e30a72539
- [net-next,v9,2/8] net: ethtool: get rid of get/set_rxfh_context functions
https://git.kernel.org/netdev/net-next/c/dcd8dbf9e734
- [net-next,v9,3/8] net: ethtool: add support for symmetric-xor RSS hash
https://git.kernel.org/netdev/net-next/c/13e59344fb9d
- [net-next,v9,4/8] ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values
https://git.kernel.org/netdev/net-next/c/20f73b60bb5c
- [net-next,v9,5/8] ice: refactor RSS configuration
https://git.kernel.org/netdev/net-next/c/dc6e44c9d6d6
- [net-next,v9,6/8] ice: refactor the FD and RSS flow ID generation
https://git.kernel.org/netdev/net-next/c/b1f5921a99ac
- [net-next,v9,7/8] ice: enable symmetric-xor RSS for Toeplitz hash function
https://git.kernel.org/netdev/net-next/c/352e9bf23813
- [net-next,v9,8/8] iavf: enable symmetric-xor RSS for Toeplitz hash function
https://git.kernel.org/netdev/net-next/c/4a3de3fb0eb6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-12-14 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 0:33 [Intel-wired-lan] [PATCH net-next v9 0/8] Support symmetric-xor RSS hash Ahmed Zaki
2023-12-13 0:33 ` [Intel-wired-lan] [PATCH net-next v9 1/8] net: ethtool: pass a pointer to parameters to get/set_rxfh ethtool ops Ahmed Zaki
2023-12-13 0:33 ` [Intel-wired-lan] [PATCH net-next v9 2/8] net: ethtool: get rid of get/set_rxfh_context functions Ahmed Zaki
2023-12-13 0:33 ` [Intel-wired-lan] [PATCH net-next v9 3/8] net: ethtool: add support for symmetric-xor RSS hash Ahmed Zaki
2023-12-13 0:33 ` [Intel-wired-lan] [PATCH net-next v9 4/8] ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values Ahmed Zaki
2023-12-13 0:33 ` [Intel-wired-lan] [PATCH net-next v9 5/8] ice: refactor RSS configuration Ahmed Zaki
2023-12-13 0:33 ` [Intel-wired-lan] [PATCH net-next v9 6/8] ice: refactor the FD and RSS flow ID generation Ahmed Zaki
2023-12-13 0:33 ` [Intel-wired-lan] [PATCH net-next v9 7/8] ice: enable symmetric-xor RSS for Toeplitz hash function Ahmed Zaki
2023-12-13 0:33 ` [Intel-wired-lan] [PATCH net-next v9 8/8] iavf: " Ahmed Zaki
2023-12-14 6:20 ` patchwork-bot+netdevbpf [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=170253482778.28524.4770397031071631009.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.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 \
--cc=willemdebruijn.kernel@gmail.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