[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YImPN7C/5BXRv6uC@shredder.lan>
Date: Wed, 28 Apr 2021 19:37:11 +0300
From: Ido Schimmel <idosch@...sch.org>
To: Pavel Balaev <balaevpa@...otecs.ru>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Jonathan Corbet <corbet@....net>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
David Ahern <dsahern@...nel.org>,
Shuah Khan <shuah@...nel.org>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
Ido Schimmel <idosch@...dia.com>
Subject: Re: [PATCH v6 net-next 3/3] selftests/net/forwarding: configurable
seed tests
On Wed, Apr 28, 2021 at 03:34:55PM +0300, Pavel Balaev wrote:
> Test equal and different seed values for IPv4/IPv6
> multipath routing.
The test does not follow the usual convention of forwarding tests that
are expected to be run with both veth pairs and loop backed physical
devices. See: tools/testing/selftests/net/forwarding/README (and
existing tests for reference)
This approach allows us to test both the software and hardware data paths.
You can construct a test where you have multiple VRFs instead of
multiple namespaces. These VRFs emulate your hosts and routers. Send
multiple flows from one host and check the distribution across the
multiple paths connecting your two routers. Change the seed, expect a
different distribution. Go back to original seed and expect the original
distribution.
Powered by blists - more mailing lists