[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231031082023.3fd4761b@kernel.org>
Date: Tue, 31 Oct 2023 08:20:23 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Gal Pressman <gal@...dia.com>
Cc: Ahmed Zaki <ahmed.zaki@...el.com>, "Alexander H Duyck"
<alexander.duyck@...il.com>, <mkubecek@...e.cz>, <andrew@...n.ch>,
<willemdebruijn.kernel@...il.com>, Wojciech Drewek
<wojciech.drewek@...el.com>, <corbet@....net>, <netdev@...r.kernel.org>,
<linux-doc@...r.kernel.org>, <jesse.brandeburg@...el.com>,
<edumazet@...gle.com>, <anthony.l.nguyen@...el.com>, <horms@...nel.org>,
<vladimir.oltean@....com>, Jacob Keller <jacob.e.keller@...el.com>,
<intel-wired-lan@...ts.osuosl.org>, <pabeni@...hat.com>,
<davem@...emloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net-next v4 1/6] net: ethtool: allow
symmetric-xor RSS hash for any flow type
On Tue, 31 Oct 2023 09:14:58 -0600 Ahmed Zaki wrote:
> Do you mean add vendor-specific implementation details to common docs?
> Not sure if I have seen this before. Any examples?
>
> Or, we can add a note in ethtool doc that each vendor's implementation
> is different and "Refer to your vendor's specifications for more info".
Gal, can you shed any more detail on who your implementation differs?
It will help the discussion, and also - I'm not sure how you can do
xor differently..
Powered by blists - more mailing lists