From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@OSS.NVIDIA.COM>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
dsahern@gmail.com, petrm@OSS.NVIDIA.COM, roopa@OSS.NVIDIA.COM,
nikolay@OSS.NVIDIA.COM, ssuryaextr@gmail.com,
mlxsw@OSS.NVIDIA.COM
Subject: Re: [PATCH net-next 00/10] Add support for custom multipath hash
Date: Tue, 18 May 2021 20:50:12 +0000 [thread overview]
Message-ID: <162137101289.13244.7446357799476667939.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210517181526.193786-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 17 May 2021 21:15:16 +0300 you wrote:
> This patchset adds support for custom multipath hash policy for both
> IPv4 and IPv6 traffic. The new policy allows user space to control the
> outer and inner packet fields used for the hash computation.
>
> Motivation
> ==========
>
> [...]
Here is the summary with links:
- [net-next,01/10] ipv4: Calculate multipath hash inside switch statement
https://git.kernel.org/netdev/net-next/c/2e68ea926841
- [net-next,02/10] ipv4: Add a sysctl to control multipath hash fields
https://git.kernel.org/netdev/net-next/c/ce5c9c20d364
- [net-next,03/10] ipv4: Add custom multipath hash policy
https://git.kernel.org/netdev/net-next/c/4253b4986f98
- [net-next,04/10] ipv6: Use a more suitable label name
https://git.kernel.org/netdev/net-next/c/67db5ca73b1f
- [net-next,05/10] ipv6: Calculate multipath hash inside switch statement
https://git.kernel.org/netdev/net-next/c/b95b6e072a92
- [net-next,06/10] ipv6: Add a sysctl to control multipath hash fields
https://git.kernel.org/netdev/net-next/c/ed13923f980e
- [net-next,07/10] ipv6: Add custom multipath hash policy
https://git.kernel.org/netdev/net-next/c/73c2c5cbb15a
- [net-next,08/10] selftests: forwarding: Add test for custom multipath hash
https://git.kernel.org/netdev/net-next/c/511e8db54036
- [net-next,09/10] selftests: forwarding: Add test for custom multipath hash with IPv4 GRE
https://git.kernel.org/netdev/net-next/c/185b0c190bb6
- [net-next,10/10] selftests: forwarding: Add test for custom multipath hash with IPv6 GRE
https://git.kernel.org/netdev/net-next/c/b7715acba4d3
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:[~2021-05-18 20:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 18:15 [PATCH net-next 00/10] Add support for custom multipath hash Ido Schimmel
2021-05-17 18:15 ` [PATCH net-next 01/10] ipv4: Calculate multipath hash inside switch statement Ido Schimmel
2021-05-18 1:39 ` David Ahern
2021-05-17 18:15 ` [PATCH net-next 02/10] ipv4: Add a sysctl to control multipath hash fields Ido Schimmel
2021-05-18 1:41 ` David Ahern
2021-05-17 18:15 ` [PATCH net-next 03/10] ipv4: Add custom multipath hash policy Ido Schimmel
2021-05-18 1:42 ` David Ahern
2021-05-17 18:15 ` [PATCH net-next 04/10] ipv6: Use a more suitable label name Ido Schimmel
2021-05-18 1:43 ` David Ahern
2021-05-17 18:15 ` [PATCH net-next 05/10] ipv6: Calculate multipath hash inside switch statement Ido Schimmel
2021-05-18 1:43 ` David Ahern
2021-05-17 18:15 ` [PATCH net-next 06/10] ipv6: Add a sysctl to control multipath hash fields Ido Schimmel
2021-05-18 1:44 ` David Ahern
2021-05-17 18:15 ` [PATCH net-next 07/10] ipv6: Add custom multipath hash policy Ido Schimmel
2021-05-18 1:45 ` David Ahern
2021-05-17 18:15 ` [PATCH net-next 08/10] selftests: forwarding: Add test for custom multipath hash Ido Schimmel
2021-05-18 1:48 ` David Ahern
2021-05-17 18:15 ` [PATCH net-next 09/10] selftests: forwarding: Add test for custom multipath hash with IPv4 GRE Ido Schimmel
2021-05-18 1:50 ` David Ahern
2021-05-17 18:15 ` [PATCH net-next 10/10] selftests: forwarding: Add test for custom multipath hash with IPv6 GRE Ido Schimmel
2021-05-18 1:50 ` David Ahern
2021-05-18 20:50 ` 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=162137101289.13244.7446357799476667939.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@OSS.NVIDIA.COM \
--cc=kuba@kernel.org \
--cc=mlxsw@OSS.NVIDIA.COM \
--cc=netdev@vger.kernel.org \
--cc=nikolay@OSS.NVIDIA.COM \
--cc=petrm@OSS.NVIDIA.COM \
--cc=roopa@OSS.NVIDIA.COM \
--cc=ssuryaextr@gmail.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).