From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V1] test_plans/large_vf: change the subcase number to 1/2/3
Date: Wed, 22 Jun 2022 17:34:37 +0000 [thread overview]
Message-ID: <20220622173437.25185-1-songx.jiale@intel.com> (raw)
subcase not in order, change the subcase number to 1/2/3.
Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
test_plans/large_vf_test_plan.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/test_plans/large_vf_test_plan.rst b/test_plans/large_vf_test_plan.rst
index 918c7563..c7f0d119 100644
--- a/test_plans/large_vf_test_plan.rst
+++ b/test_plans/large_vf_test_plan.rst
@@ -359,7 +359,7 @@ Send 1000 matched IPv6 UDP packets with random UDP sport::
Check the IPv6 UDP packets are redirected by RSS to queue [0~3] without FDIR matched ID=0x2.
-Subcase 3: negative: fail to test more than 128 VFs
+Subcase 2: negative: fail to test more than 128 VFs
---------------------------------------------------
Success to create 128 max VFs with 4 QPs per PF default::
@@ -370,7 +370,7 @@ If create 129 VFs, will report fail::
echo 129 > /sys/bus/pci/devices/0000\:60\:00.0/sriov_numvfs
-bash: echo: write error: Numerical result out of range
-Subcase 4: negative: fail to setup more than 4 queues when VF number is 128
+Subcase 3: negative: fail to setup more than 4 queues when VF number is 128
---------------------------------------------------------------------------
Create 128 max VFs.
--
2.17.1
next reply other threads:[~2022-06-22 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 17:34 Jiale Song [this message]
2022-06-29 1:40 ` lijuan.tu
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=20220622173437.25185-1-songx.jiale@intel.com \
--to=songx.jiale@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).