From: Jakub Kicinski <kuba@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: mkubecek@suse.cz, andrew@lunn.ch,
willemdebruijn.kernel@gmail.com,
Wojciech Drewek <wojciech.drewek@intel.com>,
corbet@lwn.net, netdev@vger.kernel.org,
linux-doc@vger.kernel.org, jesse.brandeburg@intel.com,
edumazet@google.com, anthony.l.nguyen@intel.com,
horms@kernel.org, vladimir.oltean@nxp.com,
Jacob Keller <jacob.e.keller@intel.com>,
intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next v4 1/6] net: ethtool: allow symmetric-xor RSS hash for any flow type
Date: Fri, 20 Oct 2023 16:49:17 -0700 [thread overview]
Message-ID: <20231020164917.69d5cd44@kernel.org> (raw)
In-Reply-To: <c2c0dbe8-eee5-4e87-a115-7424ba06d21b@intel.com>
On Fri, 20 Oct 2023 17:14:11 -0600 Ahmed Zaki wrote:
> I replied to that here:
>
> https://lore.kernel.org/all/afb4a06f-cfba-47ba-adb3-09bea7cb5f00@intel.com/
>
> I am kind of confused now so please bear with me. ethtool either sends
> "ethtool_rxfh" or "ethtool_rxnfc". AFAIK "ethtool_rxfh" is the interface
> for "ethtool -X" which is used to set the RSS algorithm. But we kind of
> agreed to go with "ethtool -U|-N" for symmetric-xor, and that uses
> "ethtool_rxnfc" (as implemented in this series).
I have no strong preference. Sounds like Alex prefers to keep it closer
to algo, which is "ethtool_rxfh".
> Do you mean use "ethtool_rxfh" instead of "ethtool_rxnfc"? how would
> that work on the ethtool user interface?
I don't know what you're asking of us. If you find the code to confusing
maybe someone at Intel can help you :|
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: <mkubecek@suse.cz>, <andrew@lunn.ch>,
<willemdebruijn.kernel@gmail.com>,
Wojciech Drewek <wojciech.drewek@intel.com>, <corbet@lwn.net>,
<netdev@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<jesse.brandeburg@intel.com>, <edumazet@google.com>,
<anthony.l.nguyen@intel.com>, <horms@kernel.org>,
<vladimir.oltean@nxp.com>,
Jacob Keller <jacob.e.keller@intel.com>,
<intel-wired-lan@lists.osuosl.org>, <pabeni@redhat.com>,
<davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net-next v4 1/6] net: ethtool: allow symmetric-xor RSS hash for any flow type
Date: Fri, 20 Oct 2023 16:49:17 -0700 [thread overview]
Message-ID: <20231020164917.69d5cd44@kernel.org> (raw)
In-Reply-To: <c2c0dbe8-eee5-4e87-a115-7424ba06d21b@intel.com>
On Fri, 20 Oct 2023 17:14:11 -0600 Ahmed Zaki wrote:
> I replied to that here:
>
> https://lore.kernel.org/all/afb4a06f-cfba-47ba-adb3-09bea7cb5f00@intel.com/
>
> I am kind of confused now so please bear with me. ethtool either sends
> "ethtool_rxfh" or "ethtool_rxnfc". AFAIK "ethtool_rxfh" is the interface
> for "ethtool -X" which is used to set the RSS algorithm. But we kind of
> agreed to go with "ethtool -U|-N" for symmetric-xor, and that uses
> "ethtool_rxnfc" (as implemented in this series).
I have no strong preference. Sounds like Alex prefers to keep it closer
to algo, which is "ethtool_rxfh".
> Do you mean use "ethtool_rxfh" instead of "ethtool_rxnfc"? how would
> that work on the ethtool user interface?
I don't know what you're asking of us. If you find the code to confusing
maybe someone at Intel can help you :|
next prev parent reply other threads:[~2023-10-20 23:49 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 15:49 [Intel-wired-lan] [PATCH net-next v4 0/6] Support symmetric RSS (Toeplitz) hash Ahmed Zaki
2023-10-16 15:49 ` Ahmed Zaki
2023-10-16 15:49 ` [Intel-wired-lan] [PATCH net-next v4 1/6] net: ethtool: allow symmetric-xor RSS hash for any flow type Ahmed Zaki
2023-10-16 15:49 ` Ahmed Zaki
2023-10-16 20:17 ` [Intel-wired-lan] " Alexander H Duyck
2023-10-16 20:17 ` Alexander H Duyck
2023-10-16 21:08 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-16 21:08 ` Ahmed Zaki
2023-10-16 22:15 ` [Intel-wired-lan] " Alexander Duyck
2023-10-16 22:15 ` Alexander Duyck
2023-10-16 22:44 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-16 22:44 ` Ahmed Zaki
2023-10-16 22:55 ` [Intel-wired-lan] " Alexander Duyck
2023-10-16 22:55 ` Alexander Duyck
2023-10-16 23:30 ` [Intel-wired-lan] " Jakub Kicinski
2023-10-16 23:30 ` Jakub Kicinski
2023-10-17 0:08 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-17 0:08 ` Ahmed Zaki
2023-10-17 18:42 ` [Intel-wired-lan] " Alexander Duyck
2023-10-17 18:42 ` Alexander Duyck
2023-10-17 19:14 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-17 19:14 ` Ahmed Zaki
2023-10-17 20:03 ` [Intel-wired-lan] " Alexander Duyck
2023-10-17 20:03 ` Alexander Duyck
2023-10-17 20:19 ` [Intel-wired-lan] " Jakub Kicinski
2023-10-17 20:19 ` Jakub Kicinski
2023-10-17 20:28 ` [Intel-wired-lan] " Alexander Duyck
2023-10-17 20:28 ` Alexander Duyck
2023-10-17 18:37 ` [Intel-wired-lan] " Alexander Duyck
2023-10-17 18:37 ` Alexander Duyck
2023-10-17 20:17 ` [Intel-wired-lan] " Jakub Kicinski
2023-10-17 20:17 ` Jakub Kicinski
2023-10-17 20:41 ` [Intel-wired-lan] " Alexander Duyck
2023-10-17 20:41 ` Alexander Duyck
2023-10-17 22:12 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-17 22:12 ` Ahmed Zaki
2023-10-18 0:34 ` Jakub Kicinski
2023-10-18 0:34 ` Jakub Kicinski
2023-10-18 18:12 ` [Intel-wired-lan] " Alexander Duyck
2023-10-18 18:12 ` Alexander Duyck
2023-10-18 23:50 ` [Intel-wired-lan] " Jakub Kicinski
2023-10-18 23:50 ` Jakub Kicinski
2023-10-20 21:24 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-20 21:24 ` Ahmed Zaki
2023-10-20 22:33 ` [Intel-wired-lan] " Jakub Kicinski
2023-10-20 22:33 ` Jakub Kicinski
2023-10-20 23:14 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-20 23:14 ` Ahmed Zaki
2023-10-20 23:49 ` Jakub Kicinski [this message]
2023-10-20 23:49 ` Jakub Kicinski
2023-10-21 0:00 ` Ahmed Zaki
2023-10-21 0:00 ` Ahmed Zaki
2023-10-29 12:25 ` Gal Pressman
2023-10-29 12:25 ` Gal Pressman
2023-10-29 12:42 ` Ahmed Zaki
2023-10-29 12:42 ` Ahmed Zaki
2023-10-29 12:48 ` Gal Pressman
2023-10-29 12:48 ` Gal Pressman
2023-10-29 16:59 ` Ahmed Zaki
2023-10-29 16:59 ` Ahmed Zaki
2023-10-31 12:00 ` Gal Pressman
2023-10-31 12:00 ` Gal Pressman
2023-10-31 14:40 ` Ahmed Zaki
2023-10-31 14:40 ` Ahmed Zaki
2023-10-31 14:45 ` Gal Pressman
2023-10-31 14:45 ` Gal Pressman
2023-10-31 15:14 ` Ahmed Zaki
2023-10-31 15:14 ` Ahmed Zaki
2023-10-31 15:20 ` Jakub Kicinski
2023-10-31 15:20 ` Jakub Kicinski
2023-10-31 16:13 ` Gal Pressman
2023-10-31 16:13 ` Gal Pressman
2023-10-31 19:57 ` Jakub Kicinski
2023-10-31 19:57 ` Jakub Kicinski
2023-10-31 16:12 ` Gal Pressman
2023-10-31 16:12 ` Gal Pressman
2023-10-31 14:59 ` Alexander Duyck
2023-10-31 14:59 ` Alexander Duyck
2023-10-31 16:11 ` Gal Pressman
2023-10-31 16:11 ` Gal Pressman
2023-10-16 15:49 ` [Intel-wired-lan] [PATCH net-next v4 2/6] ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values Ahmed Zaki
2023-10-16 15:49 ` Ahmed Zaki
2023-10-16 15:49 ` [Intel-wired-lan] [PATCH net-next v4 3/6] ice: refactor RSS configuration Ahmed Zaki
2023-10-16 15:49 ` Ahmed Zaki
2023-10-16 15:49 ` [Intel-wired-lan] [PATCH net-next v4 4/6] ice: refactor the FD and RSS flow ID generation Ahmed Zaki
2023-10-16 15:49 ` Ahmed Zaki
2023-10-16 15:49 ` [Intel-wired-lan] [PATCH net-next v4 5/6] ice: enable symmetric RSS Toeplitz hash for any flow type Ahmed Zaki
2023-10-16 15:49 ` Ahmed Zaki
2023-10-16 15:49 ` [Intel-wired-lan] [PATCH net-next v4 6/6] iavf: enable symmetric RSS Toeplitz hash Ahmed Zaki
2023-10-16 15:49 ` 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=20231020164917.69d5cd44@kernel.org \
--to=kuba@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=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--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 \
--cc=wojciech.drewek@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 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.