LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] i40e X722 RSS problem with NAT-Traversal IPsec packets
Date: Tue, 14 May 2019 12:34:44 -0400 [thread overview]
Message-ID: <20190514163443.glfjva3ofqcy7lbg@csclub.uwaterloo.ca> (raw)
In-Reply-To: <CAKgT0Uf_nqZtCnHmC=-oDFz-3PuSM6=30BvJSDiAgzK062OY6w@mail.gmail.com>
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
next prev parent reply other threads:[~2019-05-14 16:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 20:52 i40e X722 RSS problem with NAT-Traversal IPsec packets Lennart Sorensen
2019-05-01 22:52 ` [Intel-wired-lan] " Alexander Duyck
2019-05-02 15:11 ` Lennart Sorensen
2019-05-02 17:03 ` Alexander Duyck
2019-05-02 17:16 ` Lennart Sorensen
2019-05-02 17:28 ` Alexander Duyck
2019-05-02 17:55 ` Lennart Sorensen
2019-05-02 18:52 ` Lennart Sorensen
2019-05-02 20:59 ` Alexander Duyck
2019-05-03 15:14 ` Lennart Sorensen
2019-05-03 17:19 ` Alexander Duyck
2019-05-03 20:59 ` Lennart Sorensen
2019-05-13 16:55 ` Lennart Sorensen
2019-05-13 19:04 ` Alexander Duyck
2019-05-14 16:34 ` Lennart Sorensen [this message]
2019-05-16 17:10 ` Alexander Duyck
2019-05-16 18:34 ` Lennart Sorensen
2019-05-16 18:37 ` Lennart Sorensen
2019-05-16 23:32 ` Alexander Duyck
2019-05-17 16:42 ` Alexander Duyck
2019-05-17 17:23 ` Lennart Sorensen
2019-05-17 22:20 ` Alexander Duyck
2019-05-21 15:15 ` Lennart Sorensen
2019-05-21 16:51 ` Alexander Duyck
2019-05-21 17:54 ` Lennart Sorensen
2019-05-21 23:22 ` Alexander Duyck
2019-05-22 14:39 ` Lennart Sorensen
2019-06-07 14:39 ` Lennart Sorensen
2019-06-07 19:32 ` Alexander Duyck
2019-06-07 20:49 ` [E1000-devel] " Hisashi T Fujinaka
2019-06-07 22:08 ` Fujinaka, Todd
2019-06-10 19:01 ` Lennart Sorensen
2020-02-07 21:51 ` Lennart Sorensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190514163443.glfjva3ofqcy7lbg@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=alexander.duyck@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).