test suite reviews and discussions
 help / color / mirror / Atom feed
From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V1 1/2] test_plans/vhost_qemu_mtu_test_plan: modify testplan
Date: Fri, 24 Jun 2022 05:37:31 -0400	[thread overview]
Message-ID: <20220624093731.2891136-1-weix.ling@intel.com> (raw)

Delete the step 4 as no need to check the MTU value in VM's testpmd,
only need to check the MTU value in VM's kernel and vhost's testpmd.

Signed-off-by: Wei Ling <weix.ling@intel.com>
---
 test_plans/vhost_qemu_mtu_test_plan.rst | 35 ++++++++++---------------
 1 file changed, 14 insertions(+), 21 deletions(-)

diff --git a/test_plans/vhost_qemu_mtu_test_plan.rst b/test_plans/vhost_qemu_mtu_test_plan.rst
index 8b504a8d..38fead0c 100644
--- a/test_plans/vhost_qemu_mtu_test_plan.rst
+++ b/test_plans/vhost_qemu_mtu_test_plan.rst
@@ -28,27 +28,20 @@ Test Case: Test the MTU in virtio-net
     Use the qemu_2.9 or qemu 2.10 to start the VM and the VM kernel should
     grand than 4.10, set the mtu value to 9000
 
-    qemu-system-x86_64 \
-    -chardev socket,id=char0,path=./vhost-net \
-    -netdev type=vhost-user,id=netdev0,chardev=char0,vhostforce \
-    -device virtio-net-pci,netdev=netdev0,mrg_rxbuf=on,host_mtu=9000
-
-3. Check the MTU value in VM::
-
-    Use the ifconfig command to check the MTU value of
-    virtio kernel driver is 9000 in VM.
-
-4. Bind the virtio driver to igb_uio, launch testpmd in VM, and verify 
-   the mtu in port info is 9000::
- 
-    ./<build_target>/app/dpdk-testpmd -c 0x03 -n 3 \
-    -- -i --txd=512 --rxd=128 --tx-offloads=0x0 --enable-hw-vlan-strip
-    testpmd> set fwd mac
-    testpmd> start
-    testpmd> show port info 0
-
-5. Check the MTU value of virtio in testpmd on host is 9000::
+    taskset -c 32 qemu-system-x86_64  -name vm0 \
+    -enable-kvm -pidfile /tmp/.vm0.pid -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait \
+    -netdev user,id=nttsip1,hostfwd=tcp:127.0.0.1:6000-:22 -device e1000,netdev=nttsip1  \
+    -chardev socket,id=char0,path=vhost-net -netdev type=vhost-user,id=netdev0,chardev=char0,vhostforce \
+    -device virtio-net-pci,netdev=netdev0,mac=52:54:00:00:00:01,mrg_rxbuf=on,host_mtu=9000 -cpu host -smp 8 \
+    -m 8192 -object memory-backend-file,id=mem,size=8192M,mem-path=/mnt/huge,share=on -numa node,memdev=mem \
+    -mem-prealloc -chardev socket,path=/tmp/vm0_qga0.sock,server,nowait,id=vm0_qga0 -device virtio-serial \
+    -device virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0 -vnc :4 -drive file=/home/image/ubuntu2004.img
+
+3. Use the ifconfig command to check the MTU value of virtio kernel driver is 9000 in VM.
+
+4. Check the MTU value of virtio in testpmd on host is 9000::
     testpmd> show port info 1
 
-6. Repeat the step 2 ~ 5, change the mtu value to 68, 65535(the minimal value
+5. Repeat the step 2 ~ 4, change the mtu value to 68, 65535(the minimal value
    and maximum value), verify the value is changed.
+
-- 
2.25.1


                 reply	other threads:[~2022-06-24  9:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220624093731.2891136-1-weix.ling@intel.com \
    --to=weix.ling@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).