DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, david.marchand@redhat.com,
	Honnappa.Nagarahalli@arm.com, ohilyard@iol.unh.edu,
	lijuan.tu@intel.com
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [RFC PATCH v1 1/2] dts: merge DTS test_plans/pf_smoke_test_plan.rst to DPDK
Date: Wed,  6 Apr 2022 15:26:47 +0000	[thread overview]
Message-ID: <20220406152648.2916866-2-juraj.linkes@pantheon.tech> (raw)
In-Reply-To: <20220406152648.2916866-1-juraj.linkes@pantheon.tech>

---
 dts/test_plans/pf_smoke_test_plan.rst | 165 ++++++++++++++++++++++++++
 1 file changed, 165 insertions(+)
 create mode 100644 dts/test_plans/pf_smoke_test_plan.rst

diff --git a/dts/test_plans/pf_smoke_test_plan.rst b/dts/test_plans/pf_smoke_test_plan.rst
new file mode 100644
index 0000000000..ffcd210574
--- /dev/null
+++ b/dts/test_plans/pf_smoke_test_plan.rst
@@ -0,0 +1,165 @@
+.. Copyright (c) <2021>, Intel Corporation
+   All rights reserved.
+
+   Redistribution and use in source and binary forms, with or without
+   modification, are permitted provided that the following conditions
+   are met:
+
+   - Redistributions of source code must retain the above copyright
+     notice, this list of conditions and the following disclaimer.
+
+   - Redistributions in binary form must reproduce the above copyright
+     notice, this list of conditions and the following disclaimer in
+     the documentation and/or other materials provided with the
+     distribution.
+
+   - Neither the name of Intel Corporation nor the names of its
+     contributors may be used to endorse or promote products derived
+     from this software without specific prior written permission.
+
+   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+   "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+   LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+   FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+   COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+   INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+   (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+   SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+   HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+   STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+   ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+   OF THE POSSIBILITY OF SUCH DAMAGE.
+
+==================
+NIC PF Smoke Test
+==================
+
+Description
+===========
+Test the basic functions of dpdk.
+1. Port connection status.
+2. Launch testpmd normally.
+3. Basic rx and tx.
+
+Prerequisites
+=============
+
+1. Hardware:
+
+    niantic/fortville/columbiaville
+
+2. Software:
+
+    dpdk: http://dpdk.org/git/dpdk
+    scapy: http://www.secdev.org/projects/scapy/
+
+3. Compile DPDK::
+
+    CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static x86_64-native-linuxapp-gcc
+    ninja -C x86_64-native-linuxapp-gcc
+
+4. Get the pci device id of DUT, for example::
+
+    ./usertools/dpdk-devbind.py -s
+
+    0000:86:00.0 'Device 1593' if=enp134s0f0 drv=ice unused=vfio-pci
+
+7. Bind PF to dpdk driver::
+
+    modprobe vfio-pci
+    ./usertools/dpdk-devbind.py -b vfio-pci 0000:86:00.0
+
+8. Launch dpdk on PF::
+
+    ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0xf -n 4 -a 0000:86:00.0 --file-prefix=pf -- -i --rxq=4 --txq=4
+    testpmd> set fwd mac
+    testpmd> set verbose 3
+    testpmd> start
+    testpmd> show port info all
+
+Test Case 1: test enable and disable jumbo frame
+====================================================
+1. when launch dpdk on PF, add  parameter '--max-pkt-len=9600 --tx-offloads=0x00008000'
+
+2. set fwd mode is mac::
+
+    testpmd> set fwd mac
+    testpmd> set verbose 3
+    testpmd> start
+
+3. Send a packet with size 9601 bytes ::
+
+    testpmd> show port stats 0
+
+    ######################## NIC statistics for port 0  ########################
+    RX-packets: 0          RX-errors: 1         RX-bytes: 0
+    TX-packets: 0          TX-errors: 0         TX-bytes: 0
+    ############################################################################
+
+Verify that TX-bytes on port 0 and RX-bytes on port 0 are 0.
+
+4. Send a packet with size 9600 bytes ::
+
+    testpmd> show port stats 0
+
+    ######################## NIC statistics for port 0  ########################
+    RX-packets: 1          RX-errors: 0         RX-bytes: 9600
+    TX-packets: 1          TX-errors: 0         TX-bytes: 9600
+    ############################################################################
+
+Verify that TX-bytes on port 0 and RX-bytes on port 0 are 9600.
+
+5. Set mtu is 1500 ::
+
+    testpmd> port config mtu 1500
+
+6. Send a packet with size 1518 bytes ::
+
+    testpmd> show port stats 0
+
+    ######################## NIC statistics for port 0  ########################
+    RX-packets: 1          RX-errors: 0         RX-bytes: 1518
+    TX-packets: 1          TX-errors: 0         TX-bytes: 1518
+    ############################################################################
+
+Verify that TX-bytes on port 0 and RX-bytes on port 0 are 1518
+
+7. Send a packet with size 1519 bytes ::
+
+    testpmd> show port stats 0
+
+    ######################## NIC statistics for port 0  ########################
+    RX-packets: 0          RX-errors: 1         RX-bytes: 0
+    TX-packets: 0          TX-errors: 0         TX-bytes: 0
+    ############################################################################
+
+Verify that TX-bytes on port 0 and RX-bytes on port 1 are 0
+
+Test Case 2: test RSS
+====================================================
+1. set fwd mode is rxonly::
+
+    testpmd> set fwd rxonly
+    testpmd> set verbose 1
+    testpmd> start
+
+4. Send different hash types' packets with different keywords, then check rx port
+    could receive packets by different queues::
+
+      sendp([Ether(dst="00:01:23:45:67:89")/IP(src="192.168.0.4", dst=RandIP())], iface="eth3")
+
+Test Case 3: test reset RX/TX queues
+====================================================
+1. Run ``port stop all`` to stop all ports.
+
+2. Run ``port config all rxq 2`` to change the number of receiving queues to two.
+
+3. Run ``port config all txq 2`` to change the number of transmitting queues to two.
+
+4. Run ``port start all`` to restart all ports.
+
+5. Check with ``show config rxtx`` that the configuration for these parameters changed.
+
+6. Run ``start`` again to restart the forwarding, then start packet generator to transmit
+   and receive packets, and check if testpmd is able to receive and forward packets
+   successfully.
-- 
2.20.1


  reply	other threads:[~2022-04-06 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 15:26 [RFC PATCH v1 0/2] merge DTS testcase files " Juraj Linkeš
2022-04-06 15:26 ` Juraj Linkeš [this message]
2022-04-06 15:26 ` [RFC PATCH v1 2/2] dts: merge DTS tests/TestSuite_pf_smoke.py " Juraj Linkeš

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=20220406152648.2916866-2-juraj.linkes@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=ohilyard@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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).