test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Peng, Yuan" <yuan.peng@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>
Subject: Re: [dts] [PATCH]test_plans: add port stop before port reset
Date: Wed, 25 Mar 2020 03:04:33 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBF10B4@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1584944920-106111-1-git-send-email-yuan.peng@intel.com>

Applied, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Peng Yuan
> Sent: Monday, March 23, 2020 2:29 PM
> To: dts@dpdk.org
> Cc: Peng, Yuan <yuan.peng@intel.com>
> Subject: [dts] [PATCH]test_plans: add port stop before port reset
> 
> Add port stop before port reset, and add port start after port reset.
> 
> Signed-off-by: Peng Yuan <yuan.peng@intel.com>
> 
> diff --git a/test_plans/vf_pf_reset_test_plan.rst
> b/test_plans/vf_pf_reset_test_plan.rst
> index 51a3e3d..d433d71 100644
> --- a/test_plans/vf_pf_reset_test_plan.rst
> +++ b/test_plans/vf_pf_reset_test_plan.rst
> @@ -128,11 +128,11 @@ Test Case 1: vf reset -- create two vfs on one pf  9.
> Reset the vfs, run the command::
> 
>       testpmd> stop
> -     testpmd> port reset 0
> -     testpmd> port reset 1
> +     testpmd> port stop all
> +     testpmd> port reset all
> +     testpmd> port start all
>       testpmd> start
> 
> -   or just run the command "port reset all".
>     Send the same 1000 packets with scapy from tester, verify the packets can
> be
>     received by one VF and can be forward to another VF correctly,
>     check the port info::
> @@ -269,7 +269,9 @@ Test Case 4: vlan rx restore -- vf reset all ports  4.
> Reset both vfs::
> 
>       testpmd> stop
> +     testpmd> port stop all
>       testpmd> port reset all
> +     testpmd> port start all
>       testpmd> start
> 
>     Send the packets in step2 from tester, @@ -313,7 +315,9 @@ test Case 5:
> vlan rx restore -- vf reset one port  3. Pf reset, then reset vf0, send packets
> from tester::
> 
>       testpmd> stop
> +     testpmd> port stop 0
>       testpmd> port reset 0
> +     testpmd> port start 0
>       testpmd> start
>       sendp([Ether(dst="00:11:22:33:44:11")/IP()/Raw('x'*1000)], \
>       iface="ens3f0",count=1000)
> @@ -333,7 +337,9 @@ test Case 5: vlan rx restore -- vf reset one port  4.
> Reset vf1::
> 
>       testpmd> stop
> +     testpmd> port stop 1
>       testpmd> port reset 1
> +     testpmd> port start 1
>       testpmd> start
>       sendp([Ether(dst="00:11:22:33:44:11")/IP()/Raw('x'*1000)], \
>       iface="ens3f0",count=1000)
> @@ -400,7 +406,9 @@ Test Case 6: vlan rx restore -- create one vf on each
> pf  4. Reset both vfs, send packets from tester::
> 
>       testpmd> stop
> +     testpmd> port stop all
>       testpmd> port reset all
> +     testpmd> port start all
>       testpmd> start
>       sendp([Ether(dst="00:11:22:33:44:11")/IP()/Raw('x'*1000)], \
>       iface="ens3f0",count=1000)
> --
> 2.7.4


      reply	other threads:[~2020-03-25  3:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23  6:28 Peng Yuan
2020-03-25  3:04 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BBF10B4@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yuan.peng@intel.com \
    /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).