test suite reviews and discussions
 help / color / mirror / Atom feed
From: Marvin Liu <yong.liu@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH 0/4] Support additional port configuration file
Date: Fri, 23 Jan 2015 16:26:55 +0800	[thread overview]
Message-ID: <1422001619-27112-1-git-send-email-yong.liu@intel.com> (raw)

From: Yong Liu <yong.liu@intel.com>

This patch set will implement new module to support additional port config 
file. In port config file, users can specified NICs' macaddress, interface, 
numa id or peer tester pci device. Thus will support users deploy their own 
NIC validation even their NICs not supported in kernel.

In this patch set, DUT and Tester port initialize sequence will also be 
reorganized. Now DUT port initialization sequence will be scan,restore,rescan,
check with port config. Tester port initialization will only make sure all 
interface up.

This patch now only support Linux OS, will implement in FreeBSD later.

Yong Liu (4):
  framework: add new module for load port configuration file
  framework: execuction file support port config nic_type
  framework: reorganize DUT and Tester port initialize sequence
  suites: remove nic type check from testsuites

 conf/ports.cfg                      |   4 +
 execution.cfg                       |   2 +-
 framework/config.py                 |  93 ++++++++++++++++++
 framework/crb.py                    |  53 +++--------
 framework/dts.py                    |  62 +++++++-----
 framework/dut.py                    | 181 +++++++++++++++++++++++++++---------
 framework/project_dpdk.py           |  22 ++---
 framework/tester.py                 |  30 ++++++
 tests/TestSuite_blacklist.py        |   2 +-
 tests/TestSuite_checksum_offload.py |   2 +-
 tests/TestSuite_fdir.py             |  16 ++--
 tests/TestSuite_ieee1588.py         |   6 +-
 tests/TestSuite_ip_pipeline.py      |   2 +-
 tests/TestSuite_ipfrag.py           |   2 +-
 tests/TestSuite_jumboframes.py      |   2 +-
 tests/TestSuite_l2fwd.py            |   2 +-
 tests/TestSuite_l3fwd.py            |   6 +-
 tests/TestSuite_link_flowctrl.py    |   2 +-
 tests/TestSuite_multiprocess.py     |   2 +-
 tests/TestSuite_pmd.py              |   4 +-
 tests/TestSuite_pmd_bonded.py       |   2 +-
 tests/TestSuite_vlan.py             |   3 +-
 tests/TestSuite_whitelist.py        |   2 +-
 23 files changed, 352 insertions(+), 150 deletions(-)
 create mode 100644 conf/ports.cfg
 create mode 100755 framework/config.py

-- 
1.9.3

             reply	other threads:[~2015-01-23  8:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  8:26 Marvin Liu [this message]
2015-01-23  8:26 ` [dts] [PATCH 1/4] framework: add new module for load " Marvin Liu
2015-02-04  3:26   ` Qiu, Michael
2015-02-04  4:51     ` Liu, Yong
2015-01-23  8:26 ` [dts] [PATCH 2/4] framework: execuction file support port config nic_type Marvin Liu
2015-02-04  3:57   ` Qiu, Michael
2015-01-23  8:26 ` [dts] [PATCH 3/4] framework: reorganize DUT and Tester port initialize sequence Marvin Liu
2015-02-04  3:56   ` Qiu, Michael
2015-02-04  5:24     ` Liu, Yong
2015-01-23  8:26 ` [dts] [PATCH 4/4] suites: remove nic type check from testsuites Marvin Liu
2015-02-04  3:57   ` Qiu, Michael

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=1422001619-27112-1-git-send-email-yong.liu@intel.com \
    --to=yong.liu@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).