Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "Vladimir Vdovin" <deliran@verdict.gg>
To: "Ido Schimmel" <idosch@idosch.org>
Cc: <netdev@vger.kernel.org>, <dsahern@kernel.org>,
	<davem@davemloft.net>, <edumazet@google.com>,
	<linux-kselftest@vger.kernel.org>, <kuba@kernel.org>,
	<pabeni@redhat.com>, <shuah@kernel.org>, <horms@kernel.org>,
	<gnault@redhat.com>
Subject: Re: [PATCH net-next v8] net: ipv4: Cache pmtu for all packet paths if multipath enabled
Date: Thu, 07 Nov 2024 12:51:56 +0300	[thread overview]
Message-ID: <D5FURBXG9EC0.2MKP63RO0JXV2@verdict.gg> (raw)
In-Reply-To: <ZyyE473qDbLiPgx7@shredder>

On Thu Nov 7, 2024 at 12:14 PM MSK, Ido Schimmel wrote:
> On Wed, Nov 06, 2024 at 01:30:07PM +0000, Vladimir Vdovin wrote:
> > +test_pmtu_ipv4_mp_exceptions() {
> > +	setup namespaces routing multipath || return $ksft_skip
> > +
> > +	trace "${ns_a}"  veth_A-R1    "${ns_r1}" veth_R1-A \
> > +	      "${ns_r1}" veth_R1-B    "${ns_b}"  veth_B-R1 \
> > +	      "${ns_a}"  veth_A-R2    "${ns_r2}" veth_R2-A \
> > +	      "${ns_r2}" veth_R2-B    "${ns_b}"  veth_B-R2
> > +
> > +	# Set up initial MTU values
> > +	mtu "${ns_a}"  veth_A-R1 2000
> > +	mtu "${ns_r1}" veth_R1-A 2000
> > +	mtu "${ns_r1}" veth_R1-B 1500
> > +	mtu "${ns_b}"  veth_B-R1 1500
> > +
> > +	mtu "${ns_a}"  veth_A-R2 2000
> > +	mtu "${ns_r2}" veth_R2-A 2000
> > +	mtu "${ns_r2}" veth_R2-B 1500
> > +	mtu "${ns_b}"  veth_B-R2 1500
> > +
> > +	fail=0
> > +
> > +	# Ping and expect two nexthop exceptions for two routes in nh group
> > +	run_cmd ${ns_a} ping -q -M want -i 0.1 -c 1 -s 1800 "${host4_b_addr}"
> > +
> > +	# Do route lookup before checking cached exceptions.
> > +	# The following commands are needed for dst entries to be cached
> > +	# in both paths exceptions and therefore dumped to user space
> > +	# Check that exceptions have been created with the correct PMTU
> > +	pmtu="$(route_get_dst_pmtu_from_exception "${ns_a}" "${host4_b_addr}" oif veth_A-R1)"
> > +	pmtu="$(route_get_dst_pmtu_from_exception "${ns_a}" "${host4_b_addr}" oif veth_A-R2)"
>
> This overrides the first PMTU
>
> > +
> > +	check_pmtu_value "1500" "${pmtu}" "exceeding MTU (veth_A-R2)" || return 1
> > +	check_pmtu_value "1500" "${pmtu}" "exceeding MTU (veth_A-R1)" || return 1
> > +
> > +	return ${fail}
>
> And "fail" does not seem to be used anymore.
>
> Can you squash the following diff to v9?
Thanks again! Sent v9
And seems that v10 will come next day, cause I did not apply your diff and forgot to
remove fail=0 :/

>
> diff --git a/tools/testing/selftests/net/pmtu.sh b/tools/testing/selftests/net/pmtu.sh
> index 9e34b54d9c15..1b4d4c598d66 100755
> --- a/tools/testing/selftests/net/pmtu.sh
> +++ b/tools/testing/selftests/net/pmtu.sh
> @@ -2396,22 +2396,14 @@ test_pmtu_ipv4_mp_exceptions() {
>  	mtu "${ns_r2}" veth_R2-B 1500
>  	mtu "${ns_b}"  veth_B-R2 1500
>  
> -	fail=0
> -
>  	# Ping and expect two nexthop exceptions for two routes in nh group
>  	run_cmd ${ns_a} ping -q -M want -i 0.1 -c 1 -s 1800 "${host4_b_addr}"
>  
> -	# Do route lookup before checking cached exceptions.
> -	# The following commands are needed for dst entries to be cached
> -	# in both paths exceptions and therefore dumped to user space
>  	# Check that exceptions have been created with the correct PMTU
>  	pmtu="$(route_get_dst_pmtu_from_exception "${ns_a}" "${host4_b_addr}" oif veth_A-R1)"
> +	check_pmtu_value "1500" "${pmtu}" "exceeding MTU (veth_A-R1)" || return 1
>  	pmtu="$(route_get_dst_pmtu_from_exception "${ns_a}" "${host4_b_addr}" oif veth_A-R2)"
> -
>  	check_pmtu_value "1500" "${pmtu}" "exceeding MTU (veth_A-R2)" || return 1
> -	check_pmtu_value "1500" "${pmtu}" "exceeding MTU (veth_A-R1)" || return 1
> -
> -	return ${fail}
>  }
>  
>  usage() {


      reply	other threads:[~2024-11-07  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 13:30 [PATCH net-next v8] net: ipv4: Cache pmtu for all packet paths if multipath enabled Vladimir Vdovin
2024-11-06 15:44 ` David Ahern
2024-11-07  9:14 ` Ido Schimmel
2024-11-07  9:51   ` Vladimir Vdovin [this message]

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=D5FURBXG9EC0.2MKP63RO0JXV2@verdict.gg \
    --to=deliran@verdict.gg \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=gnault@redhat.com \
    --cc=horms@kernel.org \
    --cc=idosch@idosch.org \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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