From: Ido Schimmel <idosch@idosch.org>
To: Pavel Balaev <balaevpa@infotecs.ru>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>, Shuah Khan <shuah@kernel.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Ido Schimmel <idosch@nvidia.com>
Subject: Re: [PATCH v6 net-next 3/3] selftests/net/forwarding: configurable seed tests
Date: Wed, 28 Apr 2021 19:37:11 +0300 [thread overview]
Message-ID: <YImPN7C/5BXRv6uC@shredder.lan> (raw)
In-Reply-To: <YIlWbxO+AFZAFww7@rnd>
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.
next prev parent reply other threads:[~2021-04-28 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 12:34 [PATCH v6 net-next 3/3] selftests/net/forwarding: configurable seed tests Pavel Balaev
2021-04-28 16:37 ` Ido Schimmel [this message]
2021-04-28 20:29 ` David Ahern
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=YImPN7C/5BXRv6uC@shredder.lan \
--to=idosch@idosch.org \
--cc=balaevpa@infotecs.ru \
--cc=christophe.jaillet@wanadoo.fr \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/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).