From: Patrick MacArthur <pmacarth@iol.unh.edu>
To: dts@dpdk.org
Cc: dpdklab@iol.unh.edu
Subject: [dts] [PATCH for-next v2 0/5] Fixes and modifications for T-Rex integration and nic_single_core_perf
Date: Tue, 20 Mar 2018 18:20:36 -0400 [thread overview]
Message-ID: <20180320222041.17303-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.
Patch 5 automates starting T-Rex as part of the prepare_generator()
setup step, if the "start_trex" configuration option is enabled.
This patch set targets the next branch, and I have uploaded these
patches to our local open-source git server:
The following changes since commit 41685e25bedcbb1bf895c1094913aab3bf42de1e:
framework/dut: adjust memory allocation for arm64 (2018-02-08 21:27:50 +0800)
are available in the git repository at:
https://oss.iol.unh.edu/dpdk/dts.git tags/for-next-v2-trex-single-core-perf
for you to fetch changes up to 0d1c06d11777c7266677989a1200f264748322d1:
framework/pktgen: Start T-Rex during prepare_generator() (2018-03-20 18:05:08 -0400)
Patrick MacArthur (5):
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()
Changes from v1:
- Add a configuration option to pktgen.cfg; trex is only started by DTS
if the option is present and non-empty.
- Drop patch 6 which renamed the test case.
conf/pktgen.cfg | 2 +
framework/dut.py | 4 +-
framework/pktgen.py | 47 +++++++----
framework/tester.py | 11 ++-
framework/texttable.py | 145 +++++++++++++++++++++-----------
framework/virt_dut.py | 2 +-
tests/TestSuite_nic_single_core_perf.py | 31 ++-----
7 files changed, 147 insertions(+), 95 deletions(-)
--
2.14.1
next reply other threads:[~2018-03-20 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 22:20 Patrick MacArthur [this message]
2018-03-20 22:20 ` [dts] [PATCH for-next v2 1/5] framework/texttable: Update to latest upstream version Patrick MacArthur
2018-03-20 22:20 ` [dts] [PATCH for-next v2 2/5] framework: Do not attempt ping6 on T-Rex ports Patrick MacArthur
2018-03-20 22:20 ` [dts] [PATCH for-next v2 3/5] tests/TestSuite_nic_single_core_perf: Fix config parsing Patrick MacArthur
2018-03-20 22:20 ` [dts] [PATCH for-next v2 4/5] tests/TestSuite_nic_single_core_perf: Use user-specified output dir Patrick MacArthur
2018-03-28 16:19 ` Ali Alnubani
2018-03-29 18:55 ` Patrick MacArthur
2018-03-20 22:20 ` [dts] [PATCH for-next v2 5/5] framework/pktgen: Start T-Rex during prepare_generator() Patrick MacArthur
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=20180320222041.17303-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).