From: Patrick MacArthur <pmacarth@iol.unh.edu>
To: dts@dpdk.org
Cc: pmacarth@iol.unh.edu, dpdklab@iol.unh.edu
Subject: [dts] [PATCH for-next 0/6] Fixes and modifications for T-Rex integration and nic_single_core_perf
Date: Tue, 20 Feb 2018 12:26:06 -0500 [thread overview]
Message-ID: <20180220172612.11973-1-pmacarth@iol.unh.edu> (raw)
The first four patches of this series are bug fixes necessary to run the
nic_single_core_perf test in its current state in the UNH-IOL environment.
The latter two patches are proposed enhancements that may require more
discussion. Patch 5 automates starting T-Rex as part of the
prepare_generator() setup step. It currently assumes that T-Rex will be
run on the tester node; if this assumption is not correct for a given
test environment, then this patch will not be applicable and may need to
be adjusted accordingly. Patch 6 changes the nic_single_core_perf test
from a functional test to a performance test.
This patch set targets the next branch.
You can pull a branch with this patch set applied from:
https://oss.iol.unh.edu/dpdk/dts.git for-next-v1-trex-single-core-perf
Patrick MacArthur (6):
framework/texttable: Update to latest upstream version
framework: Do not attempt ping6 on T-Rex ports
tests/TestSuite_nic_single_core_perf: Fix config parsing
tests/TestSuite_nic_single_core_perf: Use user-specified output dir
framework/pktgen: Start T-Rex during prepare_generator()
tests/TestSuite_nic_single_core_perf: Fix test case name
framework/dut.py | 4 +-
framework/pktgen.py | 30 +++++--
framework/tester.py | 11 ++-
framework/texttable.py | 145 +++++++++++++++++++++-----------
framework/virt_dut.py | 2 +-
tests/TestSuite_nic_single_core_perf.py | 33 ++------
6 files changed, 137 insertions(+), 88 deletions(-)
--
2.14.1
next reply other threads:[~2018-02-20 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 17:26 Patrick MacArthur [this message]
2018-02-20 17:26 ` [dts] [PATCH for-next 1/6] framework/texttable: Update to latest upstream version Patrick MacArthur
2018-02-20 17:26 ` [dts] [PATCH for-next 2/6] framework: Do not attempt ping6 on T-Rex ports Patrick MacArthur
2018-02-20 17:26 ` [dts] [PATCH for-next 3/6] tests/TestSuite_nic_single_core_perf: Fix config parsing Patrick MacArthur
2018-02-20 17:26 ` [dts] [PATCH for-next 4/6] tests/TestSuite_nic_single_core_perf: Use user-specified output dir Patrick MacArthur
2018-02-20 17:26 ` [dts] [PATCH for-next 5/6] framework/pktgen: Start T-Rex during prepare_generator() Patrick MacArthur
2018-03-02 1:51 ` Liu, Yong
2018-02-20 17:26 ` [dts] [PATCH for-next 6/6] tests/TestSuite_nic_single_core_perf: Fix test case name Patrick MacArthur
[not found] ` <188971FCDA171749BED5DA74ABF3E6F03C123A39@SHSMSX104.ccr.corp.intel.com>
2018-03-05 9:25 ` Wang, FeiX Y
[not found] ` <188971FCDA171749BED5DA74ABF3E6F03C1239F0@SHSMSX104.ccr.corp.intel.com>
2018-03-05 9:16 ` [dts] [PATCH for-next 0/6] Fixes and modifications for T-Rex integration and nic_single_core_perf Wang, FeiX Y
2018-03-20 22:25 ` Patrick MacArthur
2018-03-21 7:28 ` Wang, FeiX Y
2018-03-23 9:03 ` Wang, FeiX Y
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=20180220172612.11973-1-pmacarth@iol.unh.edu \
--to=pmacarth@iol.unh.edu \
--cc=dpdklab@iol.unh.edu \
--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).