test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yinan <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Wang Yinan <yinan.wang@intel.com>
Subject: [dts] [PATCH 09/11 v1] test_plans: add packed ring test cases for vhost_virtio_user_interrupt
Date: Fri, 28 Feb 2020 06:09:45 +0000	[thread overview]
Message-ID: <20200228060947.26001-10-yinan.wang@intel.com> (raw)
In-Reply-To: <20200228060947.26001-1-yinan.wang@intel.com>

From: Wang Yinan <yinan.wang@intel.com>

Signed-off-by: Wang Yinan <yinan.wang@intel.com>
---
 .../vhost_virtio_user_interrupt_test_plan.rst | 88 +++++++++++++++++--
 1 file changed, 80 insertions(+), 8 deletions(-)

diff --git a/test_plans/vhost_virtio_user_interrupt_test_plan.rst b/test_plans/vhost_virtio_user_interrupt_test_plan.rst
index d948dc7..149d373 100644
--- a/test_plans/vhost_virtio_user_interrupt_test_plan.rst
+++ b/test_plans/vhost_virtio_user_interrupt_test_plan.rst
@@ -34,11 +34,13 @@
 vhost/virtio-user interrupt mode test plan
 ==========================================
 
-Virtio-user interrupt need test with l3fwd-power sample, small packets send from traffic generator to virtio side, check virtio-user cores can be wakeup status, and virtio-user cores should be sleep status after stop sending packets from traffic generator.
-This test plan cover both vhost-net and vhost-user as the backend.
+Virtio-user interrupt need test with l3fwd-power sample, small packets send from traffic generator
+to virtio side, check virtio-user cores can be wakeup status, and virtio-user cores should be sleep
+status after stop sending packets from traffic generator.This test plan cover both vhost-net and
+vhost-user as the backend.
 
-Test Case1: Virtio-user interrupt test with vhost-user as backend
-=================================================================
+Test Case1: Split ring virtio-user interrupt test with vhost-user as backend
+============================================================================
 
 flow: TG --> NIC --> Vhost --> Virtio
 
@@ -58,8 +60,8 @@ flow: TG --> NIC --> Vhost --> Virtio
 
 5. Restart sending packets with packet generator, check virtio-user related core change to wakeup status again.
 
-Test Case2: Virtio-user interrupt test with vhost-net as backend
-===============================================================================
+Test Case2: Split ring virtio-user interrupt test with vhost-net as backend
+===========================================================================
 
 flow: Tap --> Vhost-net --> Virtio
 
@@ -80,8 +82,8 @@ flow: Tap --> Vhost-net --> Virtio
 
 5. Restart sending packets with tap device, check virtio-user related core change to wakeup status again.
 
-Test Case3: LSC event between vhost-user and virtio-user
-===============================================================================
+Test Case3: LSC event between vhost-user and virtio-user with split ring
+========================================================================
 
 flow: Vhost <--> Virtio
 
@@ -106,3 +108,73 @@ flow: Vhost <--> Virtio
 
     testpmd> show port info 0
     #it should show "down"
+
+Test Case4: Packed ring virtio-user interrupt test with vhost-user as backend
+=============================================================================
+
+flow: TG --> NIC --> Vhost --> Virtio
+
+1. Bind one NIC port to igb_uio, launch testpmd with a virtual vhost device as backend::
+
+    ./testpmd -c 0x7c -n 4 --socket-mem 1024,1024 --legacy-mem --vdev 'net_vhost0,iface=vhost-net,queues=1' -- -i  --rxq=1 --txq=1
+    testpmd>start
+
+2. Start l3fwd-power with a virtio-user device::
+
+    ./l3fwd-power -c 0xc000 -n 4 --socket-mem 1024,1024 --log-level='user1,7' --no-pci --file-prefix=l3fwd-pwd \
+    --vdev=virtio_user0,path=./vhost-net,packed_vq=1 -- -p 1 -P --config="(0,0,14)" --parse-ptype
+
+3. Send packets with packet generator, check the virtio-user related core can be wakeup status.
+
+4. Stop sending packets with packet generator, check virtio-user related core change to sleep status.
+
+5. Restart sending packets with packet generator, check virtio-user related core change to wakeup status again.
+
+Test Case5: Packed ring virtio-user interrupt test with vhost-net as backend with
+=================================================================================
+
+flow: Tap --> Vhost-net --> Virtio
+
+1. Start l3fwd-power with a virtio-user device, vhost-net as backend::
+
+    ./l3fwd-power -c 0xc000 -n 4 --socket-mem 1024,1024 --legacy-mem --log-level='user1,7' --no-pci --file-prefix=l3fwd-pwd \
+    --vdev=virtio_user0,path=/dev/vhost-net,packed_vq=1 -- -p 1 -P --config="(0,0,14)" --parse-ptype
+
+2. Vhost-net will generate one tap device, normally, it's TAP0, config it and generate packets on it using pind cmd::
+
+    ifconfig tap0 up
+    ifconfig tap0 1.1.1.1
+    ping -I tap0 1.1.1.2
+
+3. Check the virtio-user related core can be wake up.
+
+4. Stop sending packets with tap device, check virtio-user related core change to sleep status.
+
+5. Restart sending packets with tap device, check virtio-user related core change to wakeup status again.
+
+Test Case6: LSC event between vhost-user and virtio-user with packed ring
+=========================================================================
+
+flow: Vhost <--> Virtio
+
+1. Start vhost-user side::
+
+    ./testpmd -c 0x3000 -n 4 --socket-mem 1024,1024 --no-pci --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=1,client=0' -- -i
+    testpmd>set fwd mac
+    testpmd>start
+
+2. Start virtio-user side::
+
+    ./testpmd -c 0xc000 -n 4 --socket-mem 1024,1024 --no-pci --file-prefix=virtio --vdev=net_virtio_user0,mac=00:01:02:03:04:05,path=./vhost-net,packed_vq=1 -- -i --tx-offloads=0x00
+    testpmd>set fwd mac
+    testpmd>start
+
+3. Check the virtio-user side link status::
+
+    testpmd> show port info 0
+    #it should show "up"
+
+4. Quit the vhost-user side with testpmd, then check the virtio-user side link status::
+
+    testpmd> show port info 0
+    #it should show "down"
-- 
2.17.1


  parent reply	other threads:[~2020-02-28 13:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28  6:09 [dts] [PATCH 00/11 v1] test_plans: add packed ring cases Yinan
2020-02-28  6:09 ` [dts] [PATCH 01/11 v1] test_plans: add packed ring cases for loopback_multi_paths_port_restart Yinan
2020-02-28  6:09 ` [dts] [PATCH 02/11 v1] test_plans: add packed ring cases for loopback_multi_queues Yinan
2020-02-28  6:09 ` [dts] [PATCH 03/11 v1] test_plans: add packed ring test case for pvp_virtio_user_2M_hugepages Yinan
2020-02-28  6:09 ` [dts] [PATCH 04/11 v1] test_plans: add packed ring cases for pvp_virtio_user_4k_pages Yinan
2020-02-28  6:09 ` [dts] [PATCH 05/11 v1] test_plans: add packed ring test case for vhost_enqueue_interrupt Yinan
2020-02-28  6:09 ` [dts] [PATCH 06/11 v1] test_plans: add packed ring test cases for vhost_event_idx_interrupt Yinan
2020-02-28  6:09 ` [dts] [PATCH 07/11 v1] test_plans: add packed ring test cases for vhost_user_live_migration Yinan
2020-02-28  6:09 ` [dts] [PATCH 08/11 v1] test_plans: add packed ring test cases for vhost_virtio_pmd_interrupt Yinan
2020-02-28  6:09 ` Yinan [this message]
2020-02-28  6:09 ` [dts] [PATCH 10/11 v1] test_plans: add test cases for virtio_event_idx_interrupt Yinan
2020-02-28  6:09 ` [dts] [PATCH 11/11 v1] test_plans: add packed ring test cases for virtio_pvp_regression Yinan
2020-03-03  7:28 ` [dts] [PATCH 00/11 v1] test_plans: add packed ring cases Tu, Lijuan

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=20200228060947.26001-10-yinan.wang@intel.com \
    --to=yinan.wang@intel.com \
    --cc=dts@dpdk.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;
as well as URLs for NNTP newsgroup(s).