From: Stefano Brivio <sbrivio@redhat•com>
To: "David S . Miller" <davem@davemloft•net>
Cc: Sabrina Dubroca <sd@queasysnail•net>,
Steffen Klassert <steffen.klassert@secunet•com>,
netdev@vger•kernel.org
Subject: [PATCH net-next 0/9] selftests: pmtu: Add further vti/vti6 MTU and PMTU tests
Date: Thu, 15 Mar 2018 17:18:20 +0100 [thread overview]
Message-ID: <cover.1521129192.git.sbrivio@redhat.com> (raw)
Patches 4/9 to 9/9 add tests to verify default MTU assignment for
vti4 and vti6 interfaces, to check that MTU values set on new
link and link changes are properly taken and validated, and to
verify PMTU exceptions on vti4 interfaces.
Patch 1/9 fixes the helper to fetch exceptions MTU to run in the
passed namespace.
Patches 2/9 and 3/9 are preparation work to make it easier to
introduce those tests.
Stefano Brivio (9):
selftests: pmtu: Use namespace command prefix to fetch route mtu
selftests: pmtu: Factor out MTU parsing helper
selftests: pmtu: Introduce support for multiple tests
selftests: pmtu: Add pmtu_vti4_default_mtu test
selftests: pmtu: Add pmtu_vti6_default_mtu test
selftests: pmtu: Add pmtu_vti4_exception test
selftests: pmtu: Add pmtu_vti4_link_add_mtu test
selftests: pmtu: Add pmtu_vti6_link_add_mtu test
selftests: pmtu: Add pmtu_vti6_link_change_mtu test
tools/testing/selftests/net/pmtu.sh | 413 +++++++++++++++++++++++++++++++-----
1 file changed, 357 insertions(+), 56 deletions(-)
--
2.15.1
next reply other threads:[~2018-03-15 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 16:18 Stefano Brivio [this message]
2018-03-15 16:18 ` [PATCH net-next 1/9] selftests: pmtu: Use namespace command prefix to fetch route mtu Stefano Brivio
2018-03-15 16:18 ` [PATCH net-next 2/9] selftests: pmtu: Factor out MTU parsing helper Stefano Brivio
2018-03-15 16:18 ` [PATCH net-next 3/9] selftests: pmtu: Introduce support for multiple tests Stefano Brivio
2018-03-16 18:06 ` David Ahern
2018-03-16 19:29 ` Stefano Brivio
2018-03-16 19:53 ` David Ahern
2018-03-16 20:03 ` Stefano Brivio
2018-03-15 16:18 ` [PATCH net-next 4/9] selftests: pmtu: Add pmtu_vti4_default_mtu test Stefano Brivio
2018-03-15 16:18 ` [PATCH net-next 5/9] selftests: pmtu: Add pmtu_vti6_default_mtu test Stefano Brivio
2018-03-15 16:18 ` [PATCH net-next 6/9] selftests: pmtu: Add pmtu_vti4_exception test Stefano Brivio
2018-03-15 16:18 ` [PATCH net-next 7/9] selftests: pmtu: Add pmtu_vti4_link_add_mtu test Stefano Brivio
2018-03-15 16:18 ` [PATCH net-next 8/9] selftests: pmtu: Add pmtu_vti6_link_add_mtu test Stefano Brivio
2018-03-15 16:18 ` [PATCH net-next 9/9] selftests: pmtu: Add pmtu_vti6_link_change_mtu test Stefano Brivio
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=cover.1521129192.git.sbrivio@redhat.com \
--to=sbrivio@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sd@queasysnail$(echo .)net \
--cc=steffen.klassert@secunet$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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