test suite reviews and discussions
 help / color / mirror / Atom feed
From: Lewei Yang <leweix.yang@intel.com>
To: dts@dpdk.org
Cc: Lewei Yang <leweix.yang@intel.com>
Subject: [dts][PATCH V1] tests/mtu_update:igc can receive packets 8 larger than MTU
Date: Wed, 24 Nov 2021 17:23:43 +0000	[thread overview]
Message-ID: <20211124172343.132742-1-leweix.yang@intel.com> (raw)

According to dpdk commit 1bb4a528c41f("ethdev: fix max Rx packet length"),
there is a miss accuracy in the MTU configuration in DPDK, packets bigger (up to 8 bytes) than requested MTU can be received.

Signed-off-by: Lewei Yang <leweix.yang@intel.com>
---
 tests/TestSuite_mtu_update.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tests/TestSuite_mtu_update.py b/tests/TestSuite_mtu_update.py
index ad13a8ab..be114759 100644
--- a/tests/TestSuite_mtu_update.py
+++ b/tests/TestSuite_mtu_update.py
@@ -239,9 +239,9 @@ class TestMtuUpdate(TestCase):
         On 1G NICs, when the jubmo frame MTU set > 1500, the software adjust it to MTU+4.
         """
         if self.nic in ["powerville", "springville", "foxville"] and packet_size > 1500:
-            self.send_packet_of_size_to_tx_port(packet_size + 4 - 1, received=True)
-            self.send_packet_of_size_to_tx_port(packet_size + 4, received=True)
-            self.send_packet_of_size_to_tx_port(packet_size + 4 + 1, received=False)
+            self.send_packet_of_size_to_tx_port(packet_size + 8 - 1, received=True)
+            self.send_packet_of_size_to_tx_port(packet_size + 8, received=True)
+            self.send_packet_of_size_to_tx_port(packet_size + 8 + 1, received=False)
         else:
             self.send_packet_of_size_to_tx_port(packet_size - 1, received=True)
             self.send_packet_of_size_to_tx_port(packet_size, received=True)
-- 
2.33.1


             reply	other threads:[~2021-11-24  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 17:23 Lewei Yang [this message]
2021-11-30  2:53 ` Tu, Lijuan
2021-12-01  6:03 ` 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=20211124172343.132742-1-leweix.yang@intel.com \
    --to=leweix.yang@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).