[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230415054855.9293-1-jdamato@fastly.com>
Date: Sat, 15 Apr 2023 05:48:53 +0000
From: Joe Damato <jdamato@...tly.com>
To: intel-wired-lan@...ts.osuosl.org
Cc: netdev@...r.kernel.org, jesse.brandeburg@...el.com,
anthony.l.nguyen@...el.com, kuba@...nel.org,
Joe Damato <jdamato@...tly.com>
Subject: [PATCH net 0/2] ixgbe: Multiple RSS bugfixes
Greetings:
This series fixes two bugs I stumbled on with ixgbe:
1. The flow hash cannot be set manually with ethool at all. Patch 1/2
addresses this by fixing what appears to be a small bug in set_rxfh in
ixgbe. See the commit message for more details.
2. Once the above patch is applied and the flow hash can be set,
resetting the flow hash to default fails if the number of queues is
greater than the number of queues supported by RSS. Other drivers (like
i40e) will reset the flowhash to use the maximum number of queues
supported by RSS even if the queue count configured is larger. In other
words: some queues will not have packets distributed to them by the RSS
hash if the queue count is too large. Patch 2/2 allows the user to reset
ixgbe to default and the flowhash is set correctly to either the
maximum number of queues supported by RSS or the configured queue count,
whichever is smaller.
I believe this is correct and it mimics the behavior of i40e;
`ethtool -X $iface default` should probably always succeed even if all the
queues cannot be utilized. See the commit message for more details and
examples.
I tested these on an ixgbe system I have access to and they appear to
work as intended, but I would appreciate a review by the experts on this
list :)
Thanks,
Joe
Joe Damato (2):
ixgbe: Allow flow hash to be set via ethtool
ixgbe: Allow ixgbe to reset default flow hash
.../net/ethernet/intel/ixgbe/ixgbe_ethtool.c | 23 ++++++++++---------
1 file changed, 12 insertions(+), 11 deletions(-)
--
2.25.1
Powered by blists - more mailing lists