mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Geliang Tang <geliangtang@gmail.com>, mptcp@lists.linux.dev
Subject: Re: [MPTCP][PATCH mptcp-next] Squash to "selftests: mptcp: add testcase for active-back"
Date: Thu, 22 Jul 2021 10:55:32 +0200	[thread overview]
Message-ID: <63bcc8e8-cd71-a117-cf9b-dc0054336e26@tessares.net> (raw)
In-Reply-To: <67cd742a1da03b8633e4837c45991860236af431.1626857584.git.geliangtang@gmail.com>

Hi Geliang,

On 21/07/2021 10:56, Geliang Tang wrote:
> Drop the debug logs and make the output aligned:

Good idea!

> 05 backup flow used, bidi, link failure syn[ ok ] - synack[ ok ] - ack[ ok ]
>                                         add[ ok ] - echo  [ ok ]
>                                         stale             [ ok ]
>                                         link usage        [ ok ]

I wonder if it would not be even clearer to display one item per line, e.g.:


05 backup flow used, bidi, link failure:
     syn        [ ok ]
     synack     [ ok ]
     ack        [ ok ]
     add        [ ok ]
     echo       [ ok ]
     stale      [ ok ]
     link usage [ ok ]
06 (...)

But that is for another patch anyway. I can look at that later when
trying to make this test more reliable by removing fixed values for
"sleep" and others if nobody is already looking at that.

> 
> Signed-off-by: Geliang Tang <geliangtang@gmail.com>
> ---
>  tools/testing/selftests/net/mptcp/mptcp_join.sh | 13 ++++++-------
>  1 file changed, 6 insertions(+), 7 deletions(-)
> 
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> index 220154cb92a7..d0518487b874 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> @@ -228,7 +228,6 @@ link_failure()
>  
>  	for l in $FAILING_LINKS; do
>  		veth="ns1eth$l"
> -		echo "link $veth down" 1>&2
>  		ip -net "$ns" link set "$veth" down
>  	done
>  }
> @@ -634,7 +633,7 @@ chk_stale_nr()
>  	local stale_nr
>  	local recover_nr
>  
> -	printf "%-39s %s" " " "stale"
> +	printf "%-39s %s" " " "stale             "
>  	stale_nr=`ip netns exec $ns nstat -as | grep MPTcpExtSubflowStale | awk '{print $2}'`
>  	[ -z "$stale_nr" ] && stale_nr=0
>  	recover_nr=`ip netns exec $ns nstat -as | grep MPTcpExtSubflowRecover | awk '{print $2}'`
> @@ -878,7 +877,7 @@ chk_link_usage()
>  	local tx_rate=$((tx_link * 100 / $tx_total))
>  	local tolerance=5
>  
> -	printf "%-39s %s" " " "link usage "
> +	printf "%-39s %s" " " "link usage        "

Do you mind if I change this when applying the patch to avoid plenty of
spaces?

  printf "%-39s %-18s" " " "stale"
  printf "%-39s %-18s" " " "link usage"

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

  reply	other threads:[~2021-07-22  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21  8:56 [MPTCP][PATCH mptcp-next] Squash to "selftests: mptcp: add testcase for active-back" Geliang Tang
2021-07-22  8:55 ` Matthieu Baerts [this message]
2021-07-22  9:28   ` Geliang Tang
2021-07-22 12:50     ` Matthieu Baerts
2021-07-22  9:29   ` Matthieu Baerts

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=63bcc8e8-cd71-a117-cf9b-dc0054336e26@tessares.net \
    --to=matthieu.baerts@tessares.net \
    --cc=geliangtang@gmail.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;
as well as URLs for NNTP newsgroup(s).