From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 4/4] network: add new test-cases with randomized message length
Date: Wed, 20 Feb 2019 09:28:54 +0100 [thread overview]
Message-ID: <20190220082854.GD15392@x230> (raw)
In-Reply-To: <1550587673-7995-5-git-send-email-alexey.kodanev@oracle.com>
Hi Alexey,
> * Change test-cases in dctcp01 (TCP). Default size changed to random size.
> * New test-cases added to tcp, sctp and udp IPsec tests
> * Updated bind_noport01
> * New tests: gre02, geneve02, macsec03, vxlan04
Commit is quite big. I know, that all is related to randomized message length.
But maybe these new tests can be added in separate commit.
> * Besides random payload changes:
> - in macsec03, replay window increased from 300 to 1000
> - vxlan04 and geneve02: new checksum testcases
> - new tests use different protocol types
> Signed-off-by: Alexey Kodanev <alexey.kodanev@oracle.com>
Reviewed-by: Petr Vorel <pvorel@suse.cz>
> ---
> runtest/net.features | 9 +
> runtest/net_stress.ipsec_dccp | 208 +++++++++++-----------
> runtest/net_stress.ipsec_sctp | 208 +++++++++++-----------
> runtest/net_stress.ipsec_tcp | 208 +++++++++++-----------
> runtest/net_stress.ipsec_udp | 212 +++++++++++-----------
> testcases/network/sockets/bind_noport01.sh | 15 ++-
> testcases/network/stress/dccp/dccp_ipsec.sh | 6 +-
> testcases/network/stress/dccp/dccp_ipsec_vti.sh | 6 +-
> testcases/network/stress/sctp/sctp_ipsec.sh | 6 +-
> testcases/network/stress/sctp/sctp_ipsec_vti.sh | 6 +-
> testcases/network/stress/tcp/tcp_ipsec.sh | 6 +-
> testcases/network/stress/tcp/tcp_ipsec_vti.sh | 6 +-
> testcases/network/stress/udp/udp_ipsec.sh | 7 +-
> testcases/network/stress/udp/udp_ipsec_vti.sh | 7 +-
> testcases/network/virt/geneve02.sh | 38 ++++
> testcases/network/virt/gre02.sh | 11 ++
> testcases/network/virt/macsec03.sh | 13 ++
> testcases/network/virt/virt_lib.sh | 10 +
> testcases/network/virt/vxlan04.sh | 39 ++++
> 19 files changed, 592 insertions(+), 429 deletions(-)
> create mode 100755 testcases/network/virt/geneve02.sh
> create mode 100755 testcases/network/virt/gre02.sh
> create mode 100755 testcases/network/virt/macsec03.sh
> create mode 100755 testcases/network/virt/vxlan04.sh
...
> +++ b/testcases/network/virt/geneve02.sh
...
> +. virt_lib.sh
> +
> +VIRT_PERF_THRESHOLD=${VIRT_PERF_THRESHOLD:-160}
VIRT_PERF_THRESHOLD is read in virt_lib.sh. So this first line does not have
to be here. That applies also for vxlan04.sh (this commit) + other testcases
which already use this variable.
> +[ "$VIRT_PERF_THRESHOLD" -lt 160 ] && VIRT_PERF_THRESHOLD=160
Kind regards,
Petr
next prev parent reply other threads:[~2019-02-20 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 14:47 [LTP] [PATCH 0/4] network: new random message size test-cases Alexey Kodanev
2019-02-19 14:47 ` [LTP] [PATCH 1/4] network/gre01: move setup to library Alexey Kodanev
2019-02-20 8:13 ` Petr Vorel
2019-02-19 14:47 ` [LTP] [PATCH 2/4] lib/tst_net.sh: add new TST_NET_MAX_PKT env variable Alexey Kodanev
2019-02-20 8:15 ` Petr Vorel
2019-02-19 14:47 ` [LTP] [PATCH 3/4] network: use TST_NET_MAX_PKT Alexey Kodanev
2019-02-20 8:16 ` Petr Vorel
2019-02-19 14:47 ` [LTP] [PATCH 4/4] network: add new test-cases with randomized message length Alexey Kodanev
2019-02-20 8:28 ` Petr Vorel [this message]
2019-02-21 16:36 ` Alexey Kodanev
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=20190220082854.GD15392@x230 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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