From: Simon Horman <horms@kernel.org>
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>,
"Stefano Brivio" <sbrivio@redhat.com>,
"Adrián Moreno" <amorenoz@redhat.com>
Subject: Re: [PATCH net-next v3 6/7] selftests: net: Use the provided dpctl rather than the vswitchd for tests.
Date: Wed, 26 Jun 2024 17:54:55 +0100 [thread overview]
Message-ID: <20240626165455.GA3104@kernel.org> (raw)
In-Reply-To: <20240625172245.233874-7-aconole@redhat.com>
On Tue, Jun 25, 2024 at 01:22:44PM -0400, Aaron Conole 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.
>
> Additionally, make sure that when the pyroute2 package is not available
> the ovs-dpctl utility will error out to properly signal an error has
> occurred and skip using the internal utility.
Hi Aaron,
I don't feel strongly about this, but it does feel like the
change to ovs-dpctl.py could live in a separate patch.
> Reviewed-by: Stefano Brivio <sbrivio@redhat.com>
> Signed-off-by: Aaron Conole <aconole@redhat.com>
The above not withstanding,
Reviewed-by: Simon Horman <horms@kernel.org>
I have tested pmtu.sh with this change on Fedora 40 both
with python3-pyroute2 installed, which uses ovs-dpctl,
and without, which uses ovs-vswitchd userspace tools.
Tested-by: Simon Horman <horms@kernel.org>
...
next prev parent reply other threads:[~2024-06-26 16:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 17:22 [PATCH net-next v3 0/7] selftests: net: Switch pmtu.sh to use the internal ovs script Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 1/7] selftests: openvswitch: Support explicit tunnel port creation Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 2/7] selftests: openvswitch: Refactor actions parsing Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 3/7] selftests: openvswitch: Add set() and set_masked() support Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 4/7] selftests: openvswitch: Add support for tunnel() key Aaron Conole
2024-06-26 16:55 ` Simon Horman
2024-06-25 17:22 ` [PATCH net-next v3 5/7] selftests: openvswitch: Support implicit ipv6 arguments Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 6/7] selftests: net: Use the provided dpctl rather than the vswitchd for tests Aaron Conole
2024-06-26 16:54 ` Simon Horman [this message]
2024-06-27 13:46 ` Aaron Conole
2024-06-25 17:22 ` [PATCH net-next v3 7/7] selftests: net: add config for openvswitch Aaron Conole
2024-06-27 23:00 ` [PATCH net-next v3 0/7] selftests: net: Switch pmtu.sh to use the internal ovs script patchwork-bot+netdevbpf
2024-06-28 15:15 ` Jakub Kicinski
2024-06-28 18:04 ` Aaron Conole
2024-06-28 23:37 ` Jakub Kicinski
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=20240626165455.GA3104@kernel.org \
--to=horms@kernel.org \
--cc=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--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=sbrivio@redhat.com \
--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).