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>,
e1000-devel@lists.sourceforge.net
Subject: Re: [Intel-wired-lan] i40e X722 RSS problem with NAT-Traversal IPsec packets
Date: Fri, 7 Feb 2020 16:51:09 -0500 [thread overview]
Message-ID: <20200207215109.ym6evogglt5atbnk@csclub.uwaterloo.ca> (raw)
In-Reply-To: <CAKgT0Ue1M8_30PVPmoJy_EGo2mjM26ecz32Myx-hpnuq_6wdjw@mail.gmail.com>
On Fri, Jun 07, 2019 at 12:32:51PM -0700, Alexander Duyck wrote:
> I had reached out to some folks over in the networking division hoping
> that they can get a reproduction as I don't have the hardware that you
> are seeing the issue on so I have no way to reproduce it.
>
> Maybe someone from that group can reply and tell us where they are on that?
Well I still never heard anything from anyone. Just installed 4.10
firmware in case that security fix (the only change to happen in over
12 months) did something, but no.
So all UDP encapsulated IPsec packets still always have RSS value of 0.
I am tempted to write a test to see if all UDP encapsulated IP packets
that are not of one of the explicitly handled types have this problem
since I have a suspicion they do.
--
Len Sorensen
prev parent reply other threads:[~2020-02-07 22:00 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
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 [this message]
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=20200207215109.ym6evogglt5atbnk@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=alexander.duyck@gmail.com \
--cc=e1000-devel@lists.sourceforge.net \
--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).