netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: netdev@vger.kernel.org, mkubecek@suse.cz,
	alexander.duyck@gmail.com, willemdebruijn.kernel@gmail.com,
	gal@nvidia.com, jesse.brandeburg@intel.com,
	anthony.l.nguyen@intel.com, davem@davemloft.net,
	edumazet@google.com, horms@kernel.org, pabeni@redhat.com,
	andrew@lunn.ch,
	Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
	Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Subject: Re: [PATCH ethtool] ethtool: add support for RSS input transformation
Date: Fri, 2 Feb 2024 11:06:14 -0800	[thread overview]
Message-ID: <20240202110614.18a0770e@kernel.org> (raw)
In-Reply-To: <20240201204104.40931-1-ahmed.zaki@intel.com>

On Thu,  1 Feb 2024 13:41:04 -0700 Ahmed Zaki wrote:
> +Sets the RSS input transformation. Currently, only the
> +.B symmetric-xor
> +transformation is supported where the NIC XORs the L3 and/or L4 source and
> +destination fields (as selected by
> +.B --config-nfc rx-flow-hash
> +) before passing them to the hash algorithm. The RSS hash function will
> +then yield the same hash for the other flow direction where the source and
> +destination fields are swapped (i.e. Symmetric RSS). Switch off (default) by
> +.B xfrm none.

Wasn't there supposed to be a warning somewhere saying that it loses
entropy?

  reply	other threads:[~2024-02-02 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 20:41 [PATCH ethtool] ethtool: add support for RSS input transformation Ahmed Zaki
2024-02-02 19:06 ` Jakub Kicinski [this message]
2024-02-02 20:04   ` 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=20240202110614.18a0770e@kernel.org \
    --to=kuba@kernel.org \
    --cc=ahmed.zaki@intel.com \
    --cc=aleksandr.loktionov@intel.com \
    --cc=alexander.duyck@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).