From: Paolo Abeni <pabeni@redhat.com>
To: Geliang Tang <geliangtang@gmail.com>, mptcp@lists.linux.dev
Cc: Geliang Tang <geliangtang@xiaomi.com>
Subject: Re: [MPTCP][PATCH v6 mptcp-next 4/5] selftests: mptcp: add fullmesh testcases
Date: Wed, 28 Jul 2021 19:21:09 +0200 [thread overview]
Message-ID: <44581bdbef617928052995d5e7ec0a6420023f9b.camel@redhat.com> (raw)
In-Reply-To: <cb461bd9ebbbfda680c2d1fea3bc7467596e3d5d.1627391588.git.geliangtang@xiaomi.com>
On Tue, 2021-07-27 at 21:24 +0800, Geliang Tang wrote:
> From: Geliang Tang <geliangtang@xiaomi.com>
>
> This patch added the testcases for the fullmesh address flag of the path
> manager.
>
> Reuse the above 10 address numbers for the fullmesh test.
>
> Signed-off-by: Geliang Tang <geliangtang@xiaomi.com>
> ---
> .../testing/selftests/net/mptcp/mptcp_join.sh | 57 ++++++++++++++++++-
> 1 file changed, 54 insertions(+), 3 deletions(-)
>
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> index 937e861e9490..2a27d6240f5b 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> @@ -367,7 +367,13 @@ do_transfer()
> fi
>
> if [ $addr_nr_ns2 -gt 0 ]; then
> - let add_nr_ns2=addr_nr_ns2
> + if [ $addr_nr_ns2 -gt 10 ]; then
> + let add_nr_ns2=addr_nr_ns2-10
> + flags=subflow,fullmesh
> + else
> + let add_nr_ns2=addr_nr_ns2
> + flags=subflow
> + fi
> counter=3
> sleep 1
> while [ $add_nr_ns2 -gt 0 ]; do
> @@ -377,7 +383,7 @@ do_transfer()
> else
> addr="10.0.$counter.2"
> fi
> - ip netns exec $ns2 ./pm_nl_ctl add $addr flags subflow
> + ip netns exec $ns2 ./pm_nl_ctl add $addr flags $flags
> let counter+=1
> let add_nr_ns2-=1
> done
> @@ -1697,6 +1703,46 @@ deny_join_id0_tests()
> chk_join_nr "subflow and address allow join id0 2" 1 1 1
> }
>
> +fullmesh_tests()
> +{
> + # fullmesh 1
> + reset
> + ip netns exec $ns1 ./pm_nl_ctl limits 0 4
> + ip netns exec $ns2 ./pm_nl_ctl limits 1 4
> + ip netns exec $ns2 ./pm_nl_ctl add 10.0.2.2 flags subflow,fullmesh
> + ip netns exec $ns2 ./pm_nl_ctl add 10.0.3.2 flags subflow,fullmesh
> + run_tests $ns1 $ns2 10.0.1.1 0 1 0 slow
> + chk_join_nr "fullmesh test 1" 4 4 4
> + chk_add_nr 1 1
> +
> + # fullmesh 2
> + reset
> + ip netns exec $ns1 ./pm_nl_ctl limits 1 3
> + ip netns exec $ns2 ./pm_nl_ctl limits 1 3
> + ip netns exec $ns1 ./pm_nl_ctl add 10.0.2.1 flags signal
> + run_tests $ns1 $ns2 10.0.1.1 0 0 11 slow
It still took me a bit follow topology creation here. I think a comment
is deserved, the first time this kind of argument is used.
Additionally, I suggest to use the "12" as an argument even in the
previous test, dropping the explicit endpoint creation, for
consistency.
All the above could use a squash-to patch, as this is the only minor
thing I have to comment for the whole series.
Thanks!
Paolo
next prev parent reply other threads:[~2021-07-28 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 13:24 [MPTCP][PATCH v6 mptcp-next 0/5] fullmesh path manager support Geliang Tang
2021-07-27 13:24 ` [MPTCP][PATCH v6 mptcp-next 1/5] mptcp: remote addresses fullmesh Geliang Tang
2021-07-27 13:24 ` [MPTCP][PATCH v6 mptcp-next 2/5] mptcp: local " Geliang Tang
2021-07-27 13:24 ` [MPTCP][PATCH v6 mptcp-next 3/5] selftests: mptcp: set and print the fullmesh flag Geliang Tang
2021-07-27 13:24 ` [MPTCP][PATCH v6 mptcp-next 4/5] selftests: mptcp: add fullmesh testcases Geliang Tang
2021-07-27 13:24 ` [MPTCP][PATCH v6 mptcp-next 5/5] selftests: mptcp: delete uncontinuous removing ids Geliang Tang
2021-07-28 17:21 ` Paolo Abeni [this message]
2021-07-28 17:41 ` [MPTCP][PATCH v6 mptcp-next 4/5] selftests: mptcp: add fullmesh testcases Matthieu Baerts
2021-07-29 7:09 ` Geliang Tang
2021-07-28 17:22 ` [MPTCP][PATCH v6 mptcp-next 0/5] fullmesh path manager support Paolo Abeni
2021-07-29 0:17 ` Mat Martineau
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=44581bdbef617928052995d5e7ec0a6420023f9b.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=geliangtang@gmail.com \
--cc=geliangtang@xiaomi.com \
--cc=mptcp@lists.linux.dev \
/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