All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Ido Schimmel <idosch@nvidia.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, petrm@nvidia.com,
	roopa@nvidia.com, nikolay@nvidia.com, ssuryaextr@gmail.com,
	mlxsw@nvidia.com
Subject: Re: [PATCH net-next 09/10] selftests: forwarding: Add test for custom multipath hash with IPv4 GRE
Date: Mon, 17 May 2021 19:50:01 -0600	[thread overview]
Message-ID: <7f6d809e-c9a7-3ef5-588f-21b71814c831@gmail.com> (raw)
In-Reply-To: <20210517181526.193786-10-idosch@nvidia.com>

On 5/17/21 12:15 PM, Ido Schimmel wrote:
> Test that when the hash policy is set to custom, traffic is distributed
> only according to the inner fields set in the fib_multipath_hash_fields
> sysctl.
> 
> Each time set a different field and make sure traffic is only
> distributed when the field is changed in the packet stream.
> 
> The test only verifies the behavior of IPv4/IPv6 overlays on top of an
> IPv4 underlay network. A subsequent patch will do the same with an IPv6
> underlay network.
> 

...

> 
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> ---
>  .../forwarding/gre_custom_multipath_hash.sh   | 456 ++++++++++++++++++
>  1 file changed, 456 insertions(+)
>  create mode 100755 tools/testing/selftests/net/forwarding/gre_custom_multipath_hash.sh
> 

Acked-by: David Ahern <dsahern@kernel.org>



  reply	other threads:[~2021-05-18  1: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 [this message]
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 ` [PATCH net-next 00/10] Add support for custom multipath hash 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=7f6d809e-c9a7-3ef5-588f-21b71814c831@gmail.com \
    --to=dsahern@gmail.com \
    --cc=davem@davemloft.net \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=petrm@nvidia.com \
    --cc=roopa@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 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.