Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp6565053yba; Tue, 14 May 2019 09:36:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqwC+e3seNrvmmIB12wSIsMV79/jcBPlMvNGcNU68FlROJsX3U70pHQVkWJlMFPyVbooDEzP X-Received: by 2002:a63:295:: with SMTP id 143mr38996490pgc.279.1557851765414; Tue, 14 May 2019 09:36:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557851765; cv=none; d=google.com; s=arc-20160816; b=ni2F4d7Dw/bG0f5vxoo9UzzrpFLKAZw9VhtcC4gG1xHK+84yjKMTW6UljeCmOIJOHp crNYCM94Odan9Z1FXi1dCnJxM0a20SOXRLGCVsoetgxJ2JN9mvBCtIgdkAv++T+6m/MP G6Yy+MCIKxLudFCqpHv267zJAIGLqh9oxQfczp3VfmOIjVnwe4J9iq8TcJW4+r1fu4zR sC21gtrAc7WWFkohh+TgLZXNPqn8SFoPAi3Uoz5LlYgr0gXrdAQ3L8dTZsmvcZHc3YOl a3rxvUT8eU4DhYiVihgGSFSD8HLEb6QSbjFNAMQ/nfcMR539BaVt24VZgfcsFpgorD4X twJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:from:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:date; bh=/ucjsyoXCnm3StG1kjHQ1TmehLxeWcu3eKTcMO9QbpU=; b=VrXGO3HPubLHdrapPsP3wRfa4xWRX4CNs+MHuCOd8+T7m9gsBcrxIF0E9OQc7SqsTb XhKPC4DeXgz/+8dSKzUoarpR8OF5cZTC/gPsSxApClAbTIGqVqx99KLBPbH/GFU3BsYN 3cUpSZN/zhwbpp3TjEDi8bcPIIUtN+ep3BEFsZ0xEGyXT235MWJVU1YkG6p6rLsXb/jE GWn2i3dKoIXmITa7rcWXr3DWdlnPgpG9kYQQNym9AK3q7M02lo014Z6fnTJFWThLw996 g3/eBE2kjl/sjIIKWcNffBBEGN9NqX4V8v8jzFgbCjm9cwoka0dMck68oV2NcUYZ8pcD enhA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=csclub.uwaterloo.ca Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x14si19891612pgl.299.2019.05.14.09.35.50; Tue, 14 May 2019 09:36:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=csclub.uwaterloo.ca Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726465AbfENQeq (ORCPT + 99 others); Tue, 14 May 2019 12:34:46 -0400 Received: from caffeine.csclub.uwaterloo.ca ([129.97.134.17]:41337 "EHLO caffeine.csclub.uwaterloo.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726036AbfENQeq (ORCPT ); Tue, 14 May 2019 12:34:46 -0400 Received: by caffeine.csclub.uwaterloo.ca (Postfix, from userid 20367) id 23294460F6A; Tue, 14 May 2019 12:34:44 -0400 (EDT) Date: Tue, 14 May 2019 12:34:44 -0400 To: Alexander Duyck Cc: Jeff Kirsher , LKML , Netdev , intel-wired-lan Subject: Re: [Intel-wired-lan] i40e X722 RSS problem with NAT-Traversal IPsec packets Message-ID: <20190514163443.glfjva3ofqcy7lbg@csclub.uwaterloo.ca> References: <20190502171636.3yquioe3gcwsxlus@csclub.uwaterloo.ca> <20190502175513.ei7kjug3az6fe753@csclub.uwaterloo.ca> <20190502185250.vlsainugtn6zjd6p@csclub.uwaterloo.ca> <20190503151421.akvmu77lghxcouni@csclub.uwaterloo.ca> <20190503205935.bg45rsso5jjj3gnx@csclub.uwaterloo.ca> <20190513165547.alkkgcsdelaznw6v@csclub.uwaterloo.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 13, 2019 at 12:04:00PM -0700, Alexander Duyck wrote: > So I recreated the first packet you listed via text2pcap, replayed it > on my test system via tcpreplay, updated my configuration to 12 > queues, and used the 2 hash keys you listed. I ended up seeing the > traffic bounce between queues 4 and 8 with an X710 I had to test with > when I was changing the key value. > > Unfortunately I don't have an X722 to test with. I'm suspecting that > there may be some difference in the RSS setup, specifically it seems > like values in the PFQF_HENA register were changed for the X722 part > that may be causing the issues we are seeing. > > I will see if I can get someone from the networking division to take a > look at this since I don't have access to the part in question nor a > datasheet for it so I am not sure if I can help much more. Great. I hope someone can figure this out because it is working very badly so far. -- Len Sorensen