From: "xu,huilong" <huilongx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,huilong" <huilongx.xu@intel.com>
Subject: [dts] [PATCH V1] fix skeleton test case failed
Date: Wed, 27 Sep 2017 17:07:42 +0800 [thread overview]
Message-ID: <1506503265-29342-3-git-send-email-huilongx.xu@intel.com> (raw)
In-Reply-To: <1506503265-29342-1-git-send-email-huilongx.xu@intel.com>
fortville25g should use 2048 mbuf size in skeleton test case
Signed-off-by: xu,huilong <huilongx.xu@intel.com>
---
tests/TestSuite_scatter.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/TestSuite_scatter.py b/tests/TestSuite_scatter.py
index 12542f7..7e27b64 100644
--- a/tests/TestSuite_scatter.py
+++ b/tests/TestSuite_scatter.py
@@ -64,7 +64,7 @@ class TestScatter(TestCase):
self.pmdout = PmdOutput(self.dut)
if self.nic in ["magnolia_park", "niantic", "sageville", "fortpark", "fortville_eagle",
- "fortville_spirit", "fortville_spirit_single",
+ "fortville_spirit", "fortville_spirit_single", "fortville_25g"
"redrockcanyou", "atwood", "boulderrapid",
"ironpond", "twinpond", "springfountain", "fortpark_TLV"]:
self.mbsize = 2048
--
1.9.3
next prev parent reply other threads:[~2017-09-27 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 9:07 [dts] [PATCH V1] fix fortville_25g dual vlan failed case xu,huilong
2017-09-27 9:07 ` [dts] [PATCH V1] fix rss key size case failed xu,huilong
2017-09-30 10:42 ` Liu, Yong
2017-09-30 11:03 ` Liu, Yong
2017-09-27 9:07 ` xu,huilong [this message]
2017-09-30 11:39 ` [dts] [PATCH V1] fix skeleton test " Liu, Yong
2017-09-27 9:07 ` [dts] [PATCH V1] fix update_system " xu,huilong
2017-09-30 11:56 ` Liu, Yong
2017-09-27 9:07 ` [dts] [PATCH V1] remove repeating check nic type xu,huilong
2017-09-30 11:45 ` Liu, Yong
2017-09-27 9:07 ` [dts] [PATCH V1] update fortville_25g check case list xu,huilong
2017-09-30 12:13 ` Liu, Yong
2017-09-30 10:35 ` [dts] [PATCH V1] fix fortville_25g dual vlan failed case Liu, Yong
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=1506503265-29342-3-git-send-email-huilongx.xu@intel.com \
--to=huilongx.xu@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).