From: patchwork-bot+netdevbpf@kernel.org
To: Louis Peens <louis.peens@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
simon.horman@corigine.com, netdev@vger.kernel.org,
oss-drivers@corigine.com
Subject: Re: [PATCH net-next] nfp: add L4 RSS hashing on UDP traffic
Date: Wed, 24 May 2023 03:40:20 +0000 [thread overview]
Message-ID: <168489962007.3716.10267854807151239349.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230522141335.22536-1-louis.peens@corigine.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 22 May 2023 16:13:35 +0200 you wrote:
> From: Jaco Coetzee <jaco.coetzee@corigine.com>
>
> Add layer 4 RSS hashing on UDP traffic to allow for the
> utilization of multiple queues for multiple connections on
> the same IP address.
>
> Previously, since the introduction of the driver, RSS hashing
> was only performed on the source and destination IP addresses
> of UDP packets thereby limiting UDP traffic to a single queue
> for multiple connections on the same IP address. The transport
> layer is now included in RSS hashing for UDP traffic, which
> was not previously the case. The reason behind the previous
> limitation is unclear - either a historic limitation of the
> NFP device, or an oversight.
>
> [...]
Here is the summary with links:
- [net-next] nfp: add L4 RSS hashing on UDP traffic
https://git.kernel.org/netdev/net-next/c/57910a47ffe9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-24 3:40 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
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 [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=168489962007.3716.10267854807151239349.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.