Re: [Intel-wired-lan] i40e X722 RSS problem with NAT-Traversal IPsec packets
From: Lennart Sorensen
Date: Mon May 13 2019 - 12:57:25 EST
On Fri, May 03, 2019 at 04:59:35PM -0400, Lennart Sorensen wrote:
> On Fri, May 03, 2019 at 10:19:47AM -0700, Alexander Duyck wrote:
> > The TCP flow could be bypassing RSS and may be using ATR to decide
> > where the Rx packets are processed. Now that I think about it there is
> > a possibility that ATR could be interfering with the queue selection.
> > You might try disabling it by running:
> > ethtool --set-priv-flags <iface> flow-director-atr off
> Hmm, I thought I had killed ATR (I certainly meant to), but it appears
> I had not. I will experiment to see if that makes a difference.
> > The problem is RSS can be bypassed for queue selection by things like
> > ATR which I called out above. One possibility is that if the
> > encryption you were using was leaving the skb->encapsulation flag set,
> > and the NIC might have misidentified the packets as something it could
> > parse and set up a bunch of rules that were rerouting incoming traffic
> > based on outgoing traffic. Disabling the feature should switch off
> > that behavior if that is in fact the case.
> > You are probably fine using 40 queues. That isn't an even power of two
> > so it would actually improve the entropy a bit since the lower bits
> > don't have a many:1 mapping to queues.
> I will let you know Monday how my tests go with atr off. I really
> thought that was off already since it was supposed to be. We always
> try to turn that off because it does not work well.
OK it took a while to try a bunch of stuff to make sure ATR really really
I still see the problem it seems.
# ethtool --show-priv-flags eth2
Private flags for eth2:
MFP : off
LinkPolling : off
veb-stats : off
hw-atr-eviction : on
legacy-rx : off
# ethtool -i eth2
firmware-version: 4.00 0x80001577 1.1767.0
Here are two packets that for some reason both go to queue 0 which
seems odd. As far as I can tell all of the packets for UDP port 4500
traffic from any IP is going to queue 0.
UDP from 10.49.1.50:4500 to 10.49.1.1:4500 encapsulating ESP:
a4bf 014e 0c88 001f 45ff f410 0800 45e0
0060 166e 4000 4011 0b1b 0af9 0132 0af9
0101 1194 1194 004c 0000 0000 0201 0000
0000 4eaf 2f76 58cd aae0 4d92 8cb7 0835
1141 7a23 9f06 f323 b816 1a2b c88d 322c
5f16 d4a6 ba72 7c89 2258 9d20 085e d6ed
c7a4 5cc1 3ef2 0753 783d b691 e9d6
UDP from 10.49.1.51:4500 to 10.49.1.1:4500 encapsulating ESP:
a4bf 014e 0c88 20f3 99ae c688 0800 45e0
0060 1671 4000 4011 0b17 0af9 0133 0af9
0101 1194 1194 004c 0000 0000 0200 0000
0000 4ec5 253f 27f1 7fdd 4d82 0697 bef2
45bd 281f 8ecf ac4f 06ed 79ba 3cbb 5eaf
494b 146e a013 8b93 1c38 8aef da3f a73d
6f13 5f80 e946 82e2 7da7 21e8 9d03
# ethtool -x eth2
RX flow hash indirection table for eth2 with 12 RX ring(s):
0: 0 1 2 3 4 5 6 7
8: 8 9 10 11 0 1 2 3
16: 4 5 6 7 8 9 10 11
488: 8 9 10 11 0 1 2 3
496: 4 5 6 7 8 9 10 11
504: 0 1 2 3 4 5 6 7
RSS hash key:
Changing the key to:
makes no change in the queue the packets are going to.