Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ahmed Zaki <ahmed.zaki@intel.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	Jakub Kicinski <kuba@kernel.org>
Cc: mkubecek@suse.cz, andrew@lunn.ch,
	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,
	intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
	davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next v2 1/6] net: ethtool: allow symmetric RSS hash for any flow type
Date: Tue, 10 Oct 2023 14:10:09 -0600	[thread overview]
Message-ID: <fa769f39-d109-47b2-bf72-218f0ae846f4@intel.com> (raw)
In-Reply-To: <CAF=yD-Kp8-iQtDM3+mgfJ6Ba0vkAeb09VZBa_k6RUequEyjd0w@mail.gmail.com>


On 2023-10-07 03:01, Willem de Bruijn wrote:
> On Fri, Oct 6, 2023 at 7:22 PM Jakub Kicinski <kuba@kernel.org> wrote:
>> On Fri,  6 Oct 2023 16:47:21 -0600 Ahmed Zaki wrote:
>>> Symmetric RSS hash functions are beneficial in applications that monitor
>>> both Tx and Rx packets of the same flow (IDS, software firewalls, ..etc).
>>> Getting all traffic of the same flow on the same RX queue results in
>>> higher CPU cache efficiency.
>>>
>>> Only fields that has counterparts in the other direction can be
>>> accepted; IP src/dst and L4 src/dst ports.
>>>
>>> The user may request RSS hash symmetry for a specific flow type, via:
>>>
>>>      # ethtool -N|-U eth0 rx-flow-hash <flow_type> s|d|f|n symmetric
>>>
>>> or turn symmetry off (asymmetric) by:
>>>
>>>      # ethtool -N|-U eth0 rx-flow-hash <flow_type> s|d|f|n
>> Thanks for the changes, code looks good!
>>
>> The question left unanswered is whether we should care about the exact
>> implementation of the symmetry (xor, xor duplicate, sort fields).
>> Toeplitz-based RSS is very precisely specified, so we may want to carry
>> that precision into the symmetric behavior. I have a weak preference
>> to do so... but no willingness to argue with you, so let me put Willem
>> on the spot and have him make a decision :)
> I do have a stronger willingness to argue, thanks ;-)
>
> Can we give a more precise name, such as symmetric-xor? In case
> another device would implement another mode, such as the symmetric
> toeplitz of __flow_hash_consistentify, it would be good to be able to
> discern the modes.

I agree that implementation matters. I changed "symmetric" to 
"symmetric-xor" in v3.

Thanks for the review.


_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-10-10 20:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 22:47 [Intel-wired-lan] [PATCH net-next v2 0/6] Support symmetric RSS (Toeplitz) hash Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [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 [this message]
2023-10-06 22:47 ` [Intel-wired-lan] [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 ` [Intel-wired-lan] [PATCH net-next v2 3/6] ice: refactor RSS configuration Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [PATCH net-next v2 4/6] ice: refactor the FD and RSS flow ID generation Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [PATCH net-next v2 5/6] ice: enable symmetric RSS Toeplitz hash for any flow type Ahmed Zaki
2023-10-06 22:47 ` [Intel-wired-lan] [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=fa769f39-d109-47b2-bf72-218f0ae846f4@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 \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox