From: Yan Xia <yanx.xia@intel.com>
To: dts@dpdk.org
Cc: Yan Xia <yanx.xia@intel.com>
Subject: [dts][PATCH V1] test/vf_jumboframe:when driver is ixgbe, dpdk does not need change
Date: Fri, 17 Dec 2021 16:46:36 +0000 [thread overview]
Message-ID: <20211217164636.22246-1-yanx.xia@intel.com> (raw)
when driver is ixgbe,dpdk does not need change
Signed-off-by: Yan Xia <yanx.xia@intel.com>
---
test_plans/vf_jumboframe_test_plan.rst | 4 ----
tests/TestSuite_vf_jumboframe.py | 5 -----
2 files changed, 9 deletions(-)
diff --git a/test_plans/vf_jumboframe_test_plan.rst b/test_plans/vf_jumboframe_test_plan.rst
index 6f8f8b6a..2f4cae3d 100644
--- a/test_plans/vf_jumboframe_test_plan.rst
+++ b/test_plans/vf_jumboframe_test_plan.rst
@@ -107,10 +107,6 @@ Testing the support of Jumbo Frames in Poll Mode Drivers consists in
configuring the maximum packet length with a value greater than 1518, and in
sending to the test machine packets with the following lengths (CRC included):
-when driver is ixgbe, turn on the jumbo_frame switch::
-
- sed -i -e 's/.jumbo_frame = .*$/.jumbo_frame = 1,/g' app/test-pmd/testpmd.c
-
#. packet length = 1518 - 1
#. packet length = 1518
diff --git a/tests/TestSuite_vf_jumboframe.py b/tests/TestSuite_vf_jumboframe.py
index 9c5db0ae..c8ae7b43 100644
--- a/tests/TestSuite_vf_jumboframe.py
+++ b/tests/TestSuite_vf_jumboframe.py
@@ -147,11 +147,6 @@ class TestVfJumboFrame(TestCase):
if self.vm_dut is None:
raise Exception("Set up VM ENV failed!")
- TESTPMD_MAIN = "app/test-pmd/testpmd.c"
- if self.kdriver == "ixgbe":
- self.vm_dut.send_expect("sed -i -e 's/.jumbo_frame = .*$/.jumbo_frame = 1,/g' %s" % TESTPMD_MAIN, "# ")
- self.vm_dut.build_install_dpdk(self.target)
-
self.vm_testpmd = PmdOutput(self.vm_dut)
except Exception as e:
--
2.33.1
next reply other threads:[~2021-12-17 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 16:46 Yan Xia [this message]
2022-01-05 8:41 ` 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=20211217164636.22246-1-yanx.xia@intel.com \
--to=yanx.xia@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).