test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Fu, JingguoX" <jingguox.fu@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [DTS][PATCH] add sageville and fortpark in settings add sageville and fortpark support in scatter suite
Date: Wed, 18 Nov 2015 02:14:14 +0000	[thread overview]
Message-ID: <6BD6202160B55B409D423293115822622BA4E2B2@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <564BD5D1.7060109@intel.com>

Those suites  not support by default, I will verify and find out which of them  support these nics and send patch to fix it,
thanks

-----Original Message-----
From: Liu, Yong 
Sent: Wednesday, November 18, 2015 9:35 AM
To: Fu, JingguoX; dts@dpdk.org
Cc: Xu, HuilongX
Subject: Re: [DTS][PATCH] add sageville and fortpark in settings add sageville and fortpark support in scatter suite

Applied. Thanks.  Just one question about sageville and fortpark, all suites beside scatter support those two Nics by default?

On 11/17/2015 05:18 PM, Jingguo Fu wrote:
> Signed-off-by: Jingguo Fu <jingguox.fu@intel.com>
> ---
>   framework/settings.py      | 3 +++
>   tests/TestSuite_scatter.py | 2 +-
>   2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/framework/settings.py b/framework/settings.py index 
> 6b02e4d..c99dcaa 100644
> --- a/framework/settings.py
> +++ b/framework/settings.py
> @@ -57,6 +57,7 @@ NICS = {
>       'ironpond': '8086:151c',
>       'twinpond': '8086:1528',
>       'twinville': '8086:1512',
> +    'sageville': '8086:1563',
>       'hartwell': '8086:10d3',
>       '82545EM': '8086:100f',
>       '82540EM': '8086:100e',
> @@ -73,6 +74,7 @@ NICS = {
>       'fortville_spirit': '8086:1583',
>       'fortville_spirit_single': '8086:1584',
>       'redrockcanyou': '8086:15a4',
> +    'fortpark':'8086:374c',
>   }
>   
>   DRIVERS = {
> @@ -87,6 +89,7 @@ DRIVERS = {
>       'ironpond': 'ixgbe',
>       'twinpond': 'ixgbe',
>       'twinville': 'ixgbe',
> +    'sageville': 'ixgbe',
>       'hartwell': 'igb',
>       '82545EM': 'igb',
>       '82540EM': 'igb',
> diff --git a/tests/TestSuite_scatter.py b/tests/TestSuite_scatter.py 
> index 3a761c4..aab2f9c 100644
> --- a/tests/TestSuite_scatter.py
> +++ b/tests/TestSuite_scatter.py
> @@ -56,7 +56,7 @@ class TestScatter(TestCase):
>           # Verify that enough ports are available
>           self.verify(len(dutPorts) >= 2, "Insufficient ports")
>           self.pmdout = PmdOutput(self.dut)
> -        if self.nic in ["niantic", "fortville_eagle", "fortville_spirit", "fortville_spirit_single", "redrockcanyou", "ironpond", "twinpond", "springfountain"]:
> +        if self.nic in ["niantic", "sageville", "fortpark", "fortville_eagle", "fortville_spirit", "fortville_spirit_single", "redrockcanyou", "ironpond", "twinpond", "springfountain"]:
>               self.mbsize = 2048
>           else:
>               self.mbsize = 1024

  reply	other threads:[~2015-11-18  2:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  9:18 Jingguo Fu
2015-11-18  1:35 ` Liu, Yong
2015-11-18  2:14   ` Fu, JingguoX [this message]
2015-11-18  3:03     ` 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=6BD6202160B55B409D423293115822622BA4E2B2@shsmsx102.ccr.corp.intel.com \
    --to=jingguox.fu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yong.liu@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).