test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Wu, ChangqingX" <changqingx.wu@intel.com>
To: "Zhu, ShuaiX" <shuaix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V2] tests/ipfrag:Modify the value to get the core.
Date: Thu, 24 Jan 2019 08:18:02 +0000	[thread overview]
Message-ID: <7F81DD3887C58F49A6B2EFEC3C28E22E0B6917EC@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1548308482-28604-1-git-send-email-shuaix.zhu@intel.com>

Tested-by: Wu, ChangqingX <changqingx.wu@intel.com>

-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhu,shuai
Sent: Thursday, January 24, 2019 1:41 PM
To: dts@dpdk.org
Cc: Zhu, ShuaiX <shuaix.zhu@intel.com>
Subject: [dts] [PATCH V2] tests/ipfrag:Modify the value to get the core.

Some platforms have only one socket, so use the minimum core number.

Signed-off-by: zhu,shuai <shuaix.zhu@intel.com>
---
 tests/TestSuite_ipfrag.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/TestSuite_ipfrag.py b/tests/TestSuite_ipfrag.py index 3a9ffb8..9f47a2c 100644
--- a/tests/TestSuite_ipfrag.py
+++ b/tests/TestSuite_ipfrag.py
@@ -92,7 +92,7 @@ class TestIpfrag(TestCase):
         self.ports_socket = self.dut.get_numa_id(ports[0])
 
         # Verify that enough threads are available
-        cores = self.dut.get_core_list("2S/2C/2T")
+        cores = self.dut.get_core_list("1S/1C/1T")
         self.verify(cores is not None, "Insufficient cores for speed testing")
 
         global P0, P1
--
2.17.2

  reply	other threads:[~2019-01-24  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24  5:41 zhu,shuai
2019-01-24  8:18 ` Wu, ChangqingX [this message]
2019-01-25  5:24 ` 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=7F81DD3887C58F49A6B2EFEC3C28E22E0B6917EC@SHSMSX101.ccr.corp.intel.com \
    --to=changqingx.wu@intel.com \
    --cc=dts@dpdk.org \
    --cc=shuaix.zhu@intel.com \
    /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).