[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190521175456.zlkiiov5hry2l4q2@csclub.uwaterloo.ca>
Date: Tue, 21 May 2019 13:54:56 -0400
From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To: Alexander Duyck <alexander.duyck@...il.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>,
intel-wired-lan <intel-wired-lan@...ts.osuosl.org>
Subject: Re: [Intel-wired-lan] i40e X722 RSS problem with NAT-Traversal IPsec
packets
On Tue, May 21, 2019 at 09:51:33AM -0700, Alexander Duyck wrote:
> I think we need to narrow this down a bit more. Let's try forcing the
> lookup table all to one value and see if traffic is still going to
> queue 0.
>
> Specifically what we need to is run the following command to try and
> force all RSS traffic to queue 8, you can verify the result with
> "ethtool -x":
> ethtool -X <iface> weight 0 0 0 0 0 0 0 0 1
>
> If that works and the IPSec traffic goes to queue 8 then we are likely
> looking at some sort of input issue, either in the parsing or the
> population of things like the input mask that we can then debug
> further.
>
> If traffic still goes to queue 0 then that tells us the output of the
> RSS hash and lookup table are being ignored, this would imply either
> some other filter is rerouting the traffic or is directing us to limit
> the queue index to 0 bits.
# ethtool -x eth2
RX flow hash indirection table for eth2 with 12 RX ring(s):
0: 7 7 7 7 7 7 7 7
8: 7 7 7 7 7 7 7 7
16: 7 7 7 7 7 7 7 7
24: 7 7 7 7 7 7 7 7
32: 7 7 7 7 7 7 7 7
...
472: 7 7 7 7 7 7 7 7
480: 7 7 7 7 7 7 7 7
488: 7 7 7 7 7 7 7 7
496: 7 7 7 7 7 7 7 7
504: 7 7 7 7 7 7 7 7
RSS hash key:
0b:1f:ae:ed:60:04:7d:e5:8a:2b:43:3f:1d:ee:6c:99:89:29:94:b0:25:db:c7:4b:fa:da:4d:3f:e8:cc:bc:00:ad:32:01:d6:1c:30:3f:f8:79:3e:f4:48:04:1f:51:d2:5a:39:f0:90
root@ECA:~# ethtool --show-priv-flags eth2
Private flags for eth2:
MFP : off
LinkPolling : off
flow-director-atr: off
veb-stats : off
hw-atr-eviction : on
legacy-rx : off
All ipsec packets are still hitting queue 0.
Seems it is completely ignoring RSS for these packets. That is
impressively weird.
--
Len Sorensen
Powered by blists - more mailing lists