From: Stefano Brivio <sbrivio@redhat.com>
To: Aaron Conole <aconole@redhat.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
"Pravin B Shelar" <pshelar@ovn.org>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Shuah Khan" <shuah@kernel.org>,
"Adrián Moreno" <amorenoz@redhat.com>,
"Simon Horman" <horms@kernel.org>
Subject: Re: [PATCH net-next 6/7] selftests: net: Use the provided dpctl rather than the vswitchd for tests.
Date: Mon, 17 Jun 2024 20:48:04 +0200 [thread overview]
Message-ID: <20240617204804.680a1254@elisabeth> (raw)
In-Reply-To: <20240617180218.1154326-7-aconole@redhat.com>
On Mon, 17 Jun 2024 14:02:17 -0400
Aaron Conole <aconole@redhat.com> wrote:
> The current pmtu test infrastucture requires an installed copy of the
> ovs-vswitchd userspace. This means that any automated or constrained
> environments may not have the requisite tools to run the tests. However,
> the pmtu tests don't require any special classifier processing. Indeed
> they are only using the vswitchd in the most basic mode - as a NORMAL
> switch.
>
> However, the ovs-dpctl kernel utility can now program all the needed basic
> flows to allow traffic to traverse the tunnels and provide support for at
> least testing some basic pmtu scenarios. More complicated flow pipelines
> can be added to the internal ovs test infrastructure, but that is work for
> the future. For now, enable the most common cases - wide mega flows with
> no other prerequisites.
>
> Enhance the pmtu testing to try testing using the internal utility, first.
> As a fallback, if the internal utility isn't running, then try with the
> ovs-vswitchd userspace tools.
Oh, nice, it looks saner than I thought. :)
> Signed-off-by: Aaron Conole <aconole@redhat.com>
> ---
> tools/testing/selftests/net/pmtu.sh | 145 +++++++++++++++++++++++-----
> 1 file changed, 123 insertions(+), 22 deletions(-)
Reviewed-by: Stefano Brivio <sbrivio@redhat.com>
--
Stefano
next prev parent reply other threads:[~2024-06-17 18:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 18:02 [PATCH net-next 0/7] selftests: net: Switch pmtu.sh to use the internal ovs script Aaron Conole
2024-06-17 18:02 ` [PATCH net-next 1/7] selftests: openvswitch: Support explicit tunnel port creation Aaron Conole
2024-06-17 18:02 ` [PATCH net-next 2/7] selftests: openvswitch: Refactor actions parsing Aaron Conole
2024-06-17 18:02 ` [PATCH net-next 3/7] selftests: openvswitch: Add set() and set_masked() support Aaron Conole
2024-06-17 18:02 ` [PATCH net-next 4/7] selftests: openvswitch: Add support for tunnel() key Aaron Conole
2024-06-17 18:02 ` [PATCH net-next 5/7] selftests: openvswitch: Support implicit ipv6 arguments Aaron Conole
2024-06-18 16:04 ` [ovs-dev] " Aaron Conole
2024-06-17 18:02 ` [PATCH net-next 6/7] selftests: net: Use the provided dpctl rather than the vswitchd for tests Aaron Conole
2024-06-17 18:48 ` Stefano Brivio [this message]
2024-06-18 16:02 ` [ovs-dev] " Aaron Conole
2024-06-17 18:02 ` [PATCH net-next 7/7] selftests: net: add config for openvswitch Aaron Conole
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=20240617204804.680a1254@elisabeth \
--to=sbrivio@redhat.com \
--cc=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.org \
--cc=shuah@kernel.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).