From: Lingli Chen <linglix.chen@intel.com>
To: dts@dpdk.org
Cc: zhiminx.huang@intel.com, Lingli Chen <linglix.chen@intel.com>
Subject: [dts][PATCH V1] tests/ieee1588: Add this test on ICE
Date: Thu, 29 Dec 2022 04:28:37 -0500 [thread overview]
Message-ID: <20221229092837.6192-1-linglix.chen@intel.com> (raw)
According to dpdk commit f5ada3bcf12d (net/ice: fix mbuf offload flag for Rx timestamp)
add ieee1588_enable on ICE.
Signed-off-by: Lingli Chen <linglix.chen@intel.com>
---
conf/test_case_checklist.json | 4 +---
tests/TestSuite_ieee1588.py | 12 +++++++++---
2 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/conf/test_case_checklist.json b/conf/test_case_checklist.json
index f88f5be1..14de236a 100644
--- a/conf/test_case_checklist.json
+++ b/conf/test_case_checklist.json
@@ -1285,9 +1285,7 @@
"NIC": [
"IGB_1G-I210_COPPER",
"cavium_a034",
- "cavium_0011",
- "ICE_25G-E810C_SFP",
- "ICE_100G-E810C_QSFP"
+ "cavium_0011"
],
"Target": [
"ALL"
diff --git a/tests/TestSuite_ieee1588.py b/tests/TestSuite_ieee1588.py
index 300d85d4..8a43a8c2 100644
--- a/tests/TestSuite_ieee1588.py
+++ b/tests/TestSuite_ieee1588.py
@@ -37,9 +37,15 @@ class TestIeee1588(TestCase):
# For IEEE1588, the full-feature tx path needs to be enabled.
# Enabling any tx offload will force DPDK utilize full tx path.
# Enabling multiple segment offload is more reasonable for user cases.
- self.pmdout.start_testpmd(
- "Default", " --tx-offloads=%s" % DEV_TX_OFFLOAD_MULTI_SEGS
- )
+ if self.kdriver == "ice":
+ self.pmdout.start_testpmd(
+ "Default",
+ " --enable-rx-timestamp --tx-offloads=%s" % DEV_TX_OFFLOAD_MULTI_SEGS,
+ )
+ else:
+ self.pmdout.start_testpmd(
+ "Default", " --tx-offloads=%s" % DEV_TX_OFFLOAD_MULTI_SEGS
+ )
def set_up(self):
"""
--
2.17.1
next reply other threads:[~2022-12-29 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 9:28 Lingli Chen [this message]
2023-01-04 1:27 ` 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=20221229092837.6192-1-linglix.chen@intel.com \
--to=linglix.chen@intel.com \
--cc=dts@dpdk.org \
--cc=zhiminx.huang@intel.com \
/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).