From: wenjieli <wenjiex.a.li@intel.com>
To: dts@dpdk.org
Cc: wenjieli <wenjiex.a.li@intel.com>
Subject: [dts] [PATCH V1] tests/shutdown_api: add the sagepond speed/duplex status in change_linkspeed
Date: Thu, 25 Oct 2018 14:04:30 +0800 [thread overview]
Message-ID: <1540447470-12750-1-git-send-email-wenjiex.a.li@intel.com> (raw)
It is NOT a DPDK issue.
With sagepond nic on DUT, after change DUT nic speed/duplex by linux commands
"ethtool -s ethX speed SPEED duplex full", the tester nic speed and duplex
will change to "Unknown" and disconnec from its peer port.
"Unknown" is expected behavior, and will not check packet forwarding.
Signed-off-by: wenjieli <wenjiex.a.li@intel.com>
---
tests/TestSuite_shutdown_api.py | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tests/TestSuite_shutdown_api.py b/tests/TestSuite_shutdown_api.py
index 52a8fbf..035d118 100644
--- a/tests/TestSuite_shutdown_api.py
+++ b/tests/TestSuite_shutdown_api.py
@@ -314,6 +314,8 @@ class TestShutdownApi(TestCase):
self.dut.send_expect("port start all", "testpmd> ", 100)
time.sleep(5) # sleep few seconds for link stable
+ if self.nic in ["sagepond"]:
+ config = ['Unknown!', 'Unknown! (255)']
for port in self.ports:
out = self.tester.send_expect(
"ethtool %s" % self.tester.get_interface(self.tester.get_local_port(port)), "# ")
@@ -322,7 +324,8 @@ class TestShutdownApi(TestCase):
self.verify("Duplex: %s" % config[1] in out,
"Wrong link type reported by the self.tester.")
self.dut.send_expect("start", "testpmd> ")
- self.check_forwarding()
+ if self.nic not in ["sagepond"]:
+ self.check_forwarding()
self.dut.send_expect("stop", "testpmd> ")
def test_enable_disablejumbo(self):
--
2.17.2
reply other threads:[~2018-10-25 6:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1540447470-12750-1-git-send-email-wenjiex.a.li@intel.com \
--to=wenjiex.a.li@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).