From: Jakub Kicinski <kuba@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, linux-doc@vger.kernel.org,
jesse.brandeburg@intel.com, edumazet@google.com,
anthony.l.nguyen@intel.com, horms@kernel.org,
vladimir.oltean@nxp.com, intel-wired-lan@lists.osuosl.org,
pabeni@redhat.com, davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next v5 0/6] Support symmetric RSS (Toeplitz) hash
Date: Wed, 18 Oct 2023 10:57:05 -0700 [thread overview]
Message-ID: <20231018105705.556a6cc9@kernel.org> (raw)
In-Reply-To: <20231018170635.65409-1-ahmed.zaki@intel.com>
On Wed, 18 Oct 2023 11:06:29 -0600 Ahmed Zaki wrote:
> v5: move sanity checks from ethtool/ioctl.c to ice's and iavf's rxfnc
> drivers entries (patches 5 and 6).
What about the discussion with Alex?
I thought you'd move the flag out of RXH_ into a separate field,
key-preproc, sub-algo, whatever..
_______________________________________________
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: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
corbet@lwn.net, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, vladimir.oltean@nxp.com,
andrew@lunn.ch, horms@kernel.org, mkubecek@suse.cz,
willemdebruijn.kernel@gmail.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v5 0/6] Support symmetric RSS (Toeplitz) hash
Date: Wed, 18 Oct 2023 10:57:05 -0700 [thread overview]
Message-ID: <20231018105705.556a6cc9@kernel.org> (raw)
In-Reply-To: <20231018170635.65409-1-ahmed.zaki@intel.com>
On Wed, 18 Oct 2023 11:06:29 -0600 Ahmed Zaki wrote:
> v5: move sanity checks from ethtool/ioctl.c to ice's and iavf's rxfnc
> drivers entries (patches 5 and 6).
What about the discussion with Alex?
I thought you'd move the flag out of RXH_ into a separate field,
key-preproc, sub-algo, whatever..
next prev parent reply other threads:[~2023-10-18 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 17:06 [Intel-wired-lan] [PATCH net-next v5 0/6] Support symmetric RSS (Toeplitz) hash Ahmed Zaki
2023-10-18 17:06 ` Ahmed Zaki
2023-10-18 17:06 ` [Intel-wired-lan] [PATCH net-next v5 1/6] net: ethtool: allow symmetric-xor RSS hash for any flow type Ahmed Zaki
2023-10-18 17:06 ` Ahmed Zaki
2023-10-18 17:06 ` [Intel-wired-lan] [PATCH net-next v5 2/6] ice: fix ICE_AQ_VSI_Q_OPT_RSS_* register values Ahmed Zaki
2023-10-18 17:06 ` Ahmed Zaki
2023-10-18 17:06 ` [Intel-wired-lan] [PATCH net-next v5 3/6] ice: refactor RSS configuration Ahmed Zaki
2023-10-18 17:06 ` Ahmed Zaki
2023-10-18 17:06 ` [Intel-wired-lan] [PATCH net-next v5 4/6] ice: refactor the FD and RSS flow ID generation Ahmed Zaki
2023-10-18 17:06 ` Ahmed Zaki
2023-10-18 17:06 ` [Intel-wired-lan] [PATCH net-next v5 5/6] ice: enable symmetric RSS Toeplitz hash for any flow type Ahmed Zaki
2023-10-18 17:06 ` Ahmed Zaki
2023-10-18 17:06 ` [Intel-wired-lan] [PATCH net-next v5 6/6] iavf: enable symmetric RSS Toeplitz hash Ahmed Zaki
2023-10-18 17:06 ` Ahmed Zaki
2023-10-18 17:57 ` Jakub Kicinski [this message]
2023-10-18 17:57 ` [PATCH net-next v5 0/6] Support symmetric RSS (Toeplitz) hash Jakub Kicinski
2023-10-18 18:21 ` [Intel-wired-lan] " Ahmed Zaki
2023-10-18 18:21 ` 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=20231018105705.556a6cc9@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=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 \
/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.