test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: Patrick MacArthur <pmacarth@iol.unh.edu>, dts@dpdk.org
Cc: dpdklab@iol.unh.edu
Subject: Re: [dts] [PATCH for-next v3 0/7] Fixes and modifications for T-Rex integration and nic_single_core_perf
Date: Fri, 30 Mar 2018 16:17:01 +0800	[thread overview]
Message-ID: <5ABDF27D.8030906@intel.com> (raw)
In-Reply-To: <20180329191605.5404-1-pmacarth@iol.unh.edu>

Thanks Patrick, applied whole patch set into next branch.

Regards,
Marvin

On 03/30/2018 03:15 AM, Patrick MacArthur wrote:
> 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.
>
> Patch 6 adds a section to the DTS getting started guide which describes
> how T-Rex should be configured for relevant tests.
>
> Patch 7 adds JSON output to the nic_single_core_perf test, which can be
> more easily consumed by automated tools.
>
> 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)

      parent reply	other threads:[~2018-03-30  0:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29 19:15 Patrick MacArthur
2018-03-29 19:15 ` [dts] [PATCH for-next v3 1/7] framework/texttable: Update to latest upstream version Patrick MacArthur
2018-03-29 19:16 ` [dts] [PATCH for-next v3 2/7] framework: Do not attempt ping6 on T-Rex ports Patrick MacArthur
2018-03-29 19:16 ` [dts] [PATCH for-next v3 3/7] tests/TestSuite_nic_single_core_perf: Fix config parsing Patrick MacArthur
2018-03-29 19:16 ` [dts] [PATCH for-next v3 4/7] tests/TestSuite_nic_single_core_perf: Use user-specified output dir Patrick MacArthur
2018-03-29 19:16 ` [dts] [PATCH for-next v3 5/7] framework/pktgen: Start T-Rex during prepare_generator() Patrick MacArthur
2018-03-29 19:16 ` [dts] [PATCH for-next v3 6/7] doc: Add T-Rex section to documentation Patrick MacArthur
2018-03-29 19:16 ` [dts] [PATCH for-next v3 7/7] tests/TestSuite_nic_single_core_perf: Report the results in JSON format Patrick MacArthur
2018-03-30  8:17 ` Liu, Yong [this message]

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=5ABDF27D.8030906@intel.com \
    --to=yong.liu@intel.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=dts@dpdk.org \
    --cc=pmacarth@iol.unh.edu \
    /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).