From: Jakub Kicinski <kuba@kernel.org>
To: Gal Pressman <gal@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"Tariq Toukan" <tariqt@nvidia.com>,
Edward Cree <ecree.xilinx@gmail.com>,
Ahmed Zaki <ahmed.zaki@intel.com>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH net-next v2 0/2] Symmetric OR-XOR RSS hash
Date: Thu, 6 Feb 2025 17:32:25 -0800 [thread overview]
Message-ID: <20250206173225.294954e2@kernel.org> (raw)
In-Reply-To: <20250205135341.542720-1-gal@nvidia.com>
On Wed, 5 Feb 2025 15:53:39 +0200 Gal Pressman wrote:
> Add support for a new type of input_xfrm: Symmetric OR-XOR.
> Symmetric OR-XOR performs hash as follows:
> (SRC_IP | DST_IP, SRC_IP ^ DST_IP, SRC_PORT | DST_PORT, SRC_PORT ^ DST_PORT)
>
> Configuration is done through ethtool -x/X command.
> For mlx5, the default is already symmetric hash, this patch now exposes
> this to userspace and allows enabling/disabling of the feature.
Please add a selftest (hw-only is fine, netdevsim can't do flow
hashing).
--
pw-bot: cr
next prev parent reply other threads:[~2025-02-07 1:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 13:53 [PATCH net-next v2 0/2] Symmetric OR-XOR RSS hash Gal Pressman
2025-02-05 13:53 ` [PATCH net-next v2 1/2] ethtool: " Gal Pressman
2025-02-05 22:20 ` Edward Cree
2025-02-07 1:31 ` Jakub Kicinski
2025-02-09 7:59 ` Gal Pressman
2025-02-05 13:53 ` [PATCH net-next v2 2/2] net/mlx5e: Symmetric OR-XOR RSS hash control Gal Pressman
2025-02-07 1:32 ` Jakub Kicinski [this message]
2025-02-09 7:59 ` [PATCH net-next v2 0/2] Symmetric OR-XOR RSS hash Gal Pressman
2025-02-11 0:27 ` Jakub Kicinski
2025-02-11 15:26 ` Gal Pressman
2025-02-12 18:13 ` Saeed Mahameed
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=20250206173225.294954e2@kernel.org \
--to=kuba@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=andrew+netdev@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=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=tariqt@nvidia.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 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.