From: Yong Liu <yong.liu@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH v2 0/4] Support additional port configuration file
Date: Wed, 4 Feb 2015 14:43:30 +0800 [thread overview]
Message-ID: <1423032214-19856-1-git-send-email-yong.liu@intel.com> (raw)
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.
v2 changes:
* Uniform load port conf function.
* Inform user that NIC driver not found in DTS.
* Fix bug port numa not cover to integer.
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 | 9 ++
execution.cfg | 2 +-
framework/config.py | 96 ++++++++++++++++++++
framework/crb.py | 66 ++++----------
framework/dts.py | 62 +++++++------
framework/dut.py | 172 +++++++++++++++++++++++++-----------
framework/project_dpdk.py | 22 ++---
framework/ssh_connection.py | 2 +-
framework/tester.py | 32 ++++++-
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 +-
24 files changed, 345 insertions(+), 173 deletions(-)
create mode 100644 conf/ports.cfg
create mode 100755 framework/config.py
--
1.9.3
next reply other threads:[~2015-02-04 6:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 6:43 Yong Liu [this message]
2015-02-04 6:43 ` [dts] [PATCH v2 1/4] framework: add new module for load " Yong Liu
2015-02-04 6:47 ` Qiu, Michael
2015-02-04 6:43 ` [dts] [PATCH v2 2/4] framework: execuction file support port config nic_type Yong Liu
2015-02-04 7:07 ` Qiu, Michael
2015-02-04 6:43 ` [dts] [PATCH v2 3/4] framework: reorganize DUT and Tester port initialize sequence Yong Liu
2015-02-04 6:59 ` Qiu, Michael
2015-02-04 6:43 ` [dts] [PATCH v2 4/4] suites: remove nic type check from testsuites Yong Liu
2015-02-04 6:50 ` Qiu, Michael
2015-02-05 1:32 ` [dts] [PATCH v2 0/4] Support additional port configuration file Liu, Yong
2015-02-05 2:18 ` [dts] [PATCH] framework: add port config pci bus id check suites: seperated checksum_offload function and performance port requirements Yong Liu
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=1423032214-19856-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).