From: Xie wei <weix.xie@intel.com>
To: dts@dpdk.org
Cc: Xie wei <weix.xie@intel.com>
Subject: [dts] [PATCH V1 2/2] tests/TestSuite_veb_switch:vf1 RX-bytes need add four bytes
Date: Wed, 6 Jan 2021 14:52:33 +0800 [thread overview]
Message-ID: <20210106065233.5401-3-weix.xie@intel.com> (raw)
In-Reply-To: <20210106065233.5401-1-weix.xie@intel.com>
DTS framework has switched i40evf to iavf, so align with it.
After testing, found that:
when send a packet which length is 60 bytes.
for iavf driver; the statistic from "show port stats 0" is: RX-bytes:56,
but set verbose 1, we can see the packet length is 60.
for i40evf driver; the statistic from "show port stats 0" is: RX-bytes: 60
Signed-off-by: Xie wei <weix.xie@intel.com>
---
tests/TestSuite_veb_switch.py | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tests/TestSuite_veb_switch.py b/tests/TestSuite_veb_switch.py
index 00dd76e7..915296ff 100644
--- a/tests/TestSuite_veb_switch.py
+++ b/tests/TestSuite_veb_switch.py
@@ -286,8 +286,7 @@ class TestVEBSwitching(TestCase):
vf0_tx_stats = self.veb_get_pmd_stats("first", 0, "tx")
vf1_rx_stats = self.veb_get_pmd_stats("second", 0, "rx")
- if self.kdriver == 'ice':
- vf1_rx_stats[-1] = vf1_rx_stats[-1] + 4
+ vf1_rx_stats[-1] = vf1_rx_stats[-1] + 4
self.verify(vf0_tx_stats[0] != 0, "no packet was sent by VF0")
self.verify(vf0_tx_stats == vf1_rx_stats, "VF1 failed to receive packets from VF0")
--
2.17.1
next prev parent reply other threads:[~2021-01-06 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 6:52 [dts] [PATCH V1 0/2] DTS framework has switched i40evf to iavf, so align with it Xie wei
2021-01-06 6:52 ` [dts] [PATCH V1 1/2] tests/TestSuite_vf_jumboframe:Rx packet size should be equal to packet size Xie wei
2021-01-07 5:16 ` Tu, Lijuan
2021-01-06 6:52 ` Xie wei [this message]
2021-01-06 6:58 ` [dts] [PATCH V1 0/2] DTS framework has switched i40evf to iavf, so align with it Xie, WeiX
2021-01-06 7:30 ` Zhao, HaiyangX
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=20210106065233.5401-3-weix.xie@intel.com \
--to=weix.xie@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).