public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Hangbin Liu <haliu@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/4] network/stress/icmp: add icmp-multi-diffip.sh to implement diffip stress test
Date: Fri, 20 May 2016 10:38:21 +0800	[thread overview]
Message-ID: <20160520023821.GI19992@Leo.nay.redhat.com> (raw)
In-Reply-To: <20160520012919.GH19992@Leo.nay.redhat.com>

On Fri, May 20, 2016 at 10:16:33AM +0800, Hangbin Liu wrote:
> > >>>+# Do Stress testing, ping flood
> > >>>+tst_resm TINFO "start ping flood stress testing"
> > >>>+for rhost_addr in ${rhost_addr_array[@]}; do
> > >>>+	for size in ${ICMP_SIZE_ARRAY}; do
> > >>>+		ping$TST_IPV6 -f -q -I $lhost_iface $rhost_addr -s $size &> /dev/null &
> > >>>+	done
> > >>>+done
> > 
> > Can we start ping test in background after adding each IP, i.e. after
> > tst_ping finished?

Ah, suddenly come in mind, If we start ping flood just after adding each IP,
there will have packets loose when we test later added IP address, which may
cause tst_ping failed. What do you think?

Thanks
Hangbin

      reply	other threads:[~2016-05-20  2:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09  7:57 [LTP] [PATCH 1/4] network/stress/icmp: add icmp-multi-diffip.sh to implement diffip stress test Hangbin Liu
2016-05-09  7:57 ` [LTP] [PATCH 2/4] network/stress/icmp: remove old multi-diffip/* tests Hangbin Liu
2016-05-09  7:57 ` [LTP] [PATCH 3/4] network/stress/icmp: add icmp-multi-diffnic.sh to implement diffnic stress test Hangbin Liu
2016-05-17 11:18   ` Alexey Kodanev
2016-05-19 13:55     ` Hangbin Liu
2016-05-09  7:57 ` [LTP] [PATCH 4/4] network/stress/icmp: remove old multi-diffnic/* tests Hangbin Liu
2016-05-17 11:46 ` [LTP] [PATCH 1/4] network/stress/icmp: add icmp-multi-diffip.sh to implement diffip stress test Alexey Kodanev
2016-05-19 14:29   ` Hangbin Liu
2016-05-19 16:01     ` Alexey Kodanev
2016-05-20  2:16       ` Hangbin Liu
2016-05-20  2:38         ` Hangbin Liu [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=20160520023821.GI19992@Leo.nay.redhat.com \
    --to=haliu@redhat.com \
    --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