netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: David Ahern <dsahern@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: forwarding: Add suppport to create veth interfaces
Date: Sun, 4 Mar 2018 10:14:53 +0200	[thread overview]
Message-ID: <20180304081453.GA2430@splinter> (raw)
In-Reply-To: <20180302164553.27319-1-dsahern@gmail.com>

On Fri, Mar 02, 2018 at 08:45:53AM -0800, David Ahern wrote:
> For tests using veth interfaces, the test infrastructure can create
> the netdevs if they do not exist. Arguably this is a preferred approach
> since the tests require p$N and p$(N+1) to be pairs.
> 
> Signed-off-by: David Ahern <dsahern@gmail.com>

[...]

> diff --git a/tools/testing/selftests/net/forwarding/lib.sh b/tools/testing/selftests/net/forwarding/lib.sh
> index d0af52109360..2ce98c6a8c25 100644
> --- a/tools/testing/selftests/net/forwarding/lib.sh
> +++ b/tools/testing/selftests/net/forwarding/lib.sh
> @@ -76,6 +76,39 @@ done
>  ##############################################################################
>  # Network interfaces configuration
>  
> +create_netif_veth()
> +{
> +	local i
> +
> +	for i in $(eval echo {1..$NUM_NETIFS}); do
> +		j=$((i+1))

local j=$((i+1)) and drop a line.

> +		ip link show dev ${NETIFS[p$i]} &> /dev/null
> +		if [[ $? -ne 0 ]]; then
> +			ip link add ${NETIFS[p$i]} type veth peer name ${NETIFS[p$j]}

Need to break this one. FWIW, I have this in my config:

$ cat ~/.vim/after/ftplugin/sh.vim
...
highlight OverLength ctermbg=red ctermfg=white
match OverLength /\%81v.\+/

Cool patch! Tested on my machine.

> +			if [[ $? -ne 0 ]]; then
> +				echo "Failed to create netif"
> +				exit 1
> +			fi
> +		fi
> +		i=$j
> +	done
> +}
> +
> +create_netif()
> +{
> +	case "$NETIF_TYPE" in
> +	veth) create_netif_veth
> +	      ;;
> +	*) echo "Can not create interfaces of type \'$NETIF_TYPE\'"
> +	   exit 1
> +	   ;;
> +	esac
> +}
> +
> +if [[ "$NETIF_CREATE" = "yes" ]]; then
> +	create_netif
> +fi
> +
>  for i in $(eval echo {1..$NUM_NETIFS}); do
>  	ip link show dev ${NETIFS[p$i]} &> /dev/null
>  	if [[ $? -ne 0 ]]; then
> -- 
> 2.11.0
> 

  reply	other threads:[~2018-03-04  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 16:45 [PATCH net-next] selftests: forwarding: Add suppport to create veth interfaces David Ahern
2018-03-04  8:14 ` Ido Schimmel [this message]
2018-03-05  1:22   ` David Ahern

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=20180304081453.GA2430@splinter \
    --to=idosch@idosch.org \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.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).