From: Jiaqi Min <jiaqix.min@intel.com>
To: dts@dpdk.org
Cc: Jiaqi Min <jiaqix.min@intel.com>
Subject: [dts] [PATCH v1] test_plans/vf_daemon: add vf jumbo frame test for ixgbe
Date: Thu, 13 Feb 2020 10:30:58 +0000 [thread overview]
Message-ID: <20200213103058.21640-1-jiaqix.min@intel.com> (raw)
add ixgbe vf jumbo frame test case
Signed-off-by: Jiaqi Min <jiaqix.min@intel.com>
---
test_plans/vf_daemon_test_plan.rst | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/test_plans/vf_daemon_test_plan.rst b/test_plans/vf_daemon_test_plan.rst
index 882e811..9a790c1 100644
--- a/test_plans/vf_daemon_test_plan.rst
+++ b/test_plans/vf_daemon_test_plan.rst
@@ -474,3 +474,28 @@ Test Case 14: Set Vlan filter for VF from PF
VF0 can receive packet
9. Send packet without vlan id to random MAC, check VF0 can receive packet
+
+Test Case 15: Ixgbe vf jumbo frame test
+=======================================
+1. Default mtu size is 1500, send one packet with length bigger than default
+ mtu size to VF0, such as 2000 from tester, check VF0 can't receive packet
+
+2. Set VF0 mtu size as 3000, but need to stop then restart port to active mtu::
+
+ testpmd> port stop all
+ testpmd> port config mtu 0 3000
+ testpmd> port start all
+ testpmd> start
+
+3. Send one packet with length 2000 from tester to VF0, check VF0 can receive packet
+
+4. Send one packet with length bigger than configured mtu size to VF0,such as 4000
+ from tester, check VF0 can't receive packet
+
+5. Quit VF0 testpmd, restart VF0 testpmd, send one packet with length 2000 from
+ tester to VF0, check VF0 can receive packet
+
+6. send one packet with length bigger than configured mtu size to VF0, such as
+ 5000 from tester, check VF0 can't receive packet
+
+notes: only x550 and x540 support jumbo frames.
--
2.17.1
next reply other threads:[~2020-02-13 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 10:30 Jiaqi Min [this message]
2020-02-27 3:20 ` He, Zhiwei
2020-02-28 1:08 ` 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=20200213103058.21640-1-jiaqix.min@intel.com \
--to=jiaqix.min@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).