diff mbox series

[V2,1/2] test_plans/telemetry:add 22.07 new feature

Message ID 20220804165855.12308-1-zhiminx.huang@intel.com (mailing list archive)
State Changes Requested
Headers
Series [V2,1/2] test_plans/telemetry:add 22.07 new feature |

Commit Message

Huang, ZhiminX Aug. 4, 2022, 4:58 p.m. UTC 
  add 22.07 new feature, support get laser power value in telemetry client.

Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
---
 test_plans/telemetry_test_plan.rst | 70 +++++++++++++++++++++++++++++-
 1 file changed, 69 insertions(+), 1 deletion(-)

Comments

Peng, Yuan Aug. 12, 2022, 6:22 a.m. UTC | #1 
Acked-by: Peng, Yuan <yuan.peng@intel.com>

-----Original Message-----
From: Zhimin Huang <zhiminx.huang@intel.com> 
Sent: Friday, August 5, 2022 12:59 AM
To: dts@dpdk.org
Cc: Huang, ZhiminX <zhiminx.huang@intel.com>
Subject: [dts][PATCH V2 1/2] test_plans/telemetry:add 22.07 new feature

add 22.07 new feature, support get laser power value in telemetry client.

Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
---
diff mbox series

Patch

diff --git a/test_plans/telemetry_test_plan.rst b/test_plans/telemetry_test_plan.rst
index 16568cd3..4034a541 100644
--- a/test_plans/telemetry_test_plan.rst
+++ b/test_plans/telemetry_test_plan.rst
@@ -200,4 +200,72 @@  Test case:  Stats of 4 ports for testpmd and telemetry with different  type nic
 	a.	Ensure # of ports stats being returned == # of ports
 	b.	Ensure packet counts (eg rx_good_packets) is 0
 	c.   Ensure extended NIC stats are shown (depends on PMD used for testing, refer to ixgbe/i40e tests for PMD xstats)
-	d.	Ensure extended NIC stats are 0 (eg: rx_q0_packets == 0)
\ No newline at end of file
+	d.	Ensure extended NIC stats are 0 (eg: rx_q0_packets == 0)
+
+Test case: read nic Laser Power via dpdk
+========================================
+
+1.Bind ports to dpdk::
+
+      ./usertools/dpdk-devbind.py --bind=vfio-pci 18:00.0 18.00.1 88:00.0 88:00.1
+
+2.Launch the dpdk testpmd with teltmetry::
+
+      ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd --telemetry  -- -i
+
+3.Launch the telemetry client::
+
+      python ./usertools/dpdk-telemetry.py
+
+4.Excute command in telemtry client::
+
+      --> /ethdev/module_eeprom,<port number>
+
+5.check the testpmd and telemetry show info same as 'ethtool -m'::
+
+      ethtool -m ens25f1 | grep 'Laser output power'
+      Laser output power                        : 0.6703 mW / -1.74 dBm
+
+Test case: check Laser Power in different optical modules
+=========================================================
+
+1.set port 0 and port 1 with diffent optical modules
+
+2.Launch the dpdk testpmd with teltmetry::
+
+      ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd --telemetry  -- -i
+
+3.Launch the telemetry client::
+
+      python ./usertools/dpdk-telemetry.py
+
+4.Excute command in telemtry client::
+
+      --> /ethdev/module_eeprom,0
+      --> /ethdev/module_eeprom,1
+
+5.check port 0 and port 1 have different Laser Power
+
+Test case: check Laser Power in same optical modules
+====================================================
+
+1.set port 0 and port 1 with same optical modules
+
+2.Launch the dpdk testpmd with teltmetry::
+
+      ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd --telemetry  -- -i
+
+3.Launch the telemetry client::
+
+      python ./usertools/dpdk-telemetry.py
+
+4.Excute command in telemtry client::
+
+      --> /ethdev/module_eeprom,0
+      --> /ethdev/module_eeprom,1
+
+5.check port 0 and port 1 have same Laser Power
+
+.. note::
+
+   the laser power will change slightly with the voltage and temperature