From: Paolo Abeni <pabeni@redhat.com>
To: Paul Blakey <paulb@nvidia.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Vlad Buslov <vladbu@nvidia.com>, Oz Shlomo <ozsh@nvidia.com>,
Roi Dayan <roid@nvidia.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>
Cc: Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net v4 2/2] selftests: add selftest for chaining of tc ingress handling to egress
Date: Thu, 13 Oct 2022 11:28:02 +0200 [thread overview]
Message-ID: <4610af6c1fbd27e7fb8f19f64514dd34de4fa437.camel@redhat.com> (raw)
In-Reply-To: <1665563053-29263-3-git-send-email-paulb@nvidia.com>
Hello,
On Wed, 2022-10-12 at 11:24 +0300, Paul Blakey wrote:
> This test runs a simple ingress tc setup between two veth pairs,
> then adds a egress->ingress rule to test the chaining of tc ingress
> pipeline to tc egress piepline.
>
> Signed-off-by: Paul Blakey <paulb@nvidia.com>
this patch does not apply cleanly to -net, could you please rebase it?
> ---
> tools/testing/selftests/net/Makefile | 1 +
> .../net/test_ingress_egress_chaining.sh | 81 +++++++++++++++++++
> 2 files changed, 82 insertions(+)
> create mode 100644 tools/testing/selftests/net/test_ingress_egress_chaining.sh
>
> diff --git a/tools/testing/selftests/net/Makefile b/tools/testing/selftests/net/Makefile
> index c0ee2955fe54..f4774717c5b6 100644
> --- a/tools/testing/selftests/net/Makefile
> +++ b/tools/testing/selftests/net/Makefile
> @@ -63,6 +63,7 @@ TEST_GEN_FILES += cmsg_sender
> TEST_GEN_FILES += stress_reuseport_listen
> TEST_PROGS += test_vxlan_vnifiltering.sh
> TEST_GEN_FILES += io_uring_zerocopy_tx
> +TEST_PROGS += test_ingress_egress_chaining.sh
>
> TEST_FILES := settings
>
> diff --git a/tools/testing/selftests/net/test_ingress_egress_chaining.sh b/tools/testing/selftests/net/test_ingress_egress_chaining.sh
> new file mode 100644
> index 000000000000..193d92078ae0
> --- /dev/null
> +++ b/tools/testing/selftests/net/test_ingress_egress_chaining.sh
> @@ -0,0 +1,81 @@
> +#!/bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +
> +# This test runs a simple ingress tc setup between two veth pairs,
> +# and chains a single egress rule to test ingress chaining to egress.
> +#
> +# Kselftest framework requirement - SKIP code is 4.
> +ksft_skip=4
> +
> +if [ "$(id -u)" -ne 0 ];then
> + echo "SKIP: Need root privileges"
> + exit $ksft_skip
> +fi
> +
> +needed_mods="act_mirred cls_flower sch_ingress"
> +for mod in $needed_mods; do
> + modinfo $mod &>/dev/null || { echo "SKIP: Need act_mirred module"; exit $ksft_skip; }
> +done
> +
> +ns="ns$((RANDOM%899+100))"
> +veth1="veth1$((RANDOM%899+100))"
> +veth2="veth2$((RANDOM%899+100))"
> +peer1="peer1$((RANDOM%899+100))"
> +peer2="peer2$((RANDOM%899+100))"
> +ip_peer1=198.51.100.5
> +ip_peer2=198.51.100.6
> +
> +function fail() {
> + echo "FAIL: $@" >> /dev/stderr
> + exit 1
> +}
> +
> +function cleanup() {
> + killall -q -9 udpgso_bench_rx
> + ip link del $veth1 &> /dev/null
> + ip link del $veth2 &> /dev/null
> + ip netns del $ns &> /dev/null
> +}
> +trap cleanup EXIT
> +
> +function config() {
> + echo "Setup veth pairs [$veth1, $peer1], and veth pair [$veth2, $peer2]"
> + ip link add $veth1 type veth peer name $peer1
> + ip link add $veth2 type veth peer name $peer2
> + ip addr add $ip_peer1/24 dev $peer1
> + ip link set $peer1 up
> + ip netns add $ns
> + ip link set dev $peer2 netns $ns
> + ip netns exec $ns ip addr add $ip_peer2/24 dev $peer2
> + ip netns exec $ns ip link set $peer2 up
> + ip link set $veth1 up
> + ip link set $veth2 up
> +
> + echo "Add tc filter ingress->egress forwarding $veth1 <-> $veth2"
> + tc qdisc add dev $veth2 ingress
> + tc qdisc add dev $veth1 ingress
> + tc filter add dev $veth2 ingress prio 1 proto all flower \
> + action mirred egress redirect dev $veth1
> + tc filter add dev $veth1 ingress prio 1 proto all flower \
> + action mirred egress redirect dev $veth2
> +
> + echo "Add tc filter egress->ingress forwarding $peer1 -> $veth1, bypassing the veth pipe"
> + tc qdisc add dev $peer1 clsact
> + tc filter add dev $peer1 egress prio 20 proto ip flower \
> + action mirred ingress redirect dev $veth1
> +}
> +
> +function test_run() {
> + echo "Run tcp traffic"
> + ./udpgso_bench_rx -t &
> + sleep 1
> + ip netns exec $ns timeout -k 2 10 ./udpgso_bench_tx -t -l 2 -4 -D $ip_peer1 || fail "traffic failed"
> + echo "Test passed"
> +}
> +
> +config
> +test_run
> +trap - EXIT
> +cleanup
> +
> +
Additionally, please remote the trailing blank line,
Thanks!
Paolo
next prev parent reply other threads:[~2022-10-13 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 8:24 [PATCH net v4 0/2] net: Fix return value of qdisc ingress handling on success Paul Blakey
2022-10-12 8:24 ` [PATCH net v4 1/2] " Paul Blakey
2022-10-12 8:24 ` [PATCH net v4 2/2] selftests: add selftest for chaining of tc ingress handling to egress Paul Blakey
2022-10-13 9:28 ` Paolo Abeni [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-18 7:34 [PATCH net v4 0/2] net: Fix return value of qdisc ingress handling on success Paul Blakey
2022-10-18 7:34 ` [PATCH net v4 2/2] selftests: add selftest for chaining of tc ingress handling to egress Paul Blakey
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=4610af6c1fbd27e7fb8f19f64514dd34de4fa437.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ozsh@nvidia.com \
--cc=paulb@nvidia.com \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=vladbu@nvidia.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 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).