From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <simon.horman@corigine.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
Louis Peens <louis.peens@corigine.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, oss-drivers@corigine.com,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next] nfp: add L4 RSS hashing on UDP traffic
Date: Wed, 24 May 2023 08:22:16 -0700 [thread overview]
Message-ID: <20230524082216.1e1fed93@kernel.org> (raw)
In-Reply-To: <ZG31Plb6/UF3XKd3@corigine.com>
On Wed, 24 May 2023 13:30:06 +0200 Simon Horman wrote:
> On Tue, May 23, 2023 at 02:20:05PM -0700, Jakub Kicinski wrote:
> > Yup, that's the exact reason it was disabled by default, FWIW.
> >
> > The Microsoft spec is not crystal clear on how to handles this:
> > https://learn.microsoft.com/en-us/windows-hardware/drivers/network/rss-hashing-types#ndis_hash_ipv4
> > There is a note saying:
> >
> > If a NIC receives a packet that has both IP and TCP headers,
> > NDIS_HASH_TCP_IPV4 should not always be used. In the case of a
> > fragmented IP packet, NDIS_HASH_IPV4 must be used. This includes
> > the first fragment which contains both IP and TCP headers.
> >
> > While NDIS_HASH_UDP_IPV4 makes no such distinction and talks only about
> > "presence" of the header.
> >
> > Maybe we should document that device is expected not to use the UDP
> > header if MF is set?
>
> Yes, maybe.
>
> Could you suggest where such documentation should go?
That's the hardest question, perhaps :)
Documentation/networking/scaling.rst and/or OCP NIC spec:
https://ocp-all.groups.io/g/OCP-Networking/topic/nic_software_core_offloads/98930671?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,98930671,previd%3D1684255676674808204,nextid%3D1676673801962532335&previd=1684255676674808204&nextid=1676673801962532335
next prev parent reply other threads:[~2023-05-24 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 14:13 [PATCH net-next] nfp: add L4 RSS hashing on UDP traffic Louis Peens
2023-05-23 10:49 ` Paolo Abeni
2023-05-23 21:20 ` Jakub Kicinski
2023-05-24 11:30 ` Simon Horman
2023-05-24 15:22 ` Jakub Kicinski [this message]
2023-05-24 15:33 ` Willem de Bruijn
2023-05-24 15:38 ` Jakub Kicinski
2023-05-24 16:14 ` Paolo Abeni
2023-05-24 16:28 ` Jakub Kicinski
2023-05-24 3:40 ` patchwork-bot+netdevbpf
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=20230524082216.1e1fed93@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=willemb@google.com \
/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).