From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Rami Rosen <ramirose@gmail.com>, Jeremy Plsek <jplsek@iol.unh.edu>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] Question about performance test
Date: Tue, 8 Jan 2019 07:06:26 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9FE870@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAHLOa7Q-_dpa7992URAy7UotQwyaqV=Dz3gdGTNVR2H6qmd+hA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
Hi Rami,
nic_single_core_perf_test is in the next branch of dts, so it can’t be found in the master branch.
Since next branch is to rework packet generator module to support a software packet generator called TREX.
A software packet generator is easily to set up with little resources comparing with hardware packet generator, IXIA.
From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of Rami Rosen
Sent: Tuesday, January 8, 2019 2:40 PM
To: Jeremy Plsek <jplsek@iol.unh.edu>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] Question about performance test
Hi Jeremy,
>At the moment, we only run performance tests. Specifically the nic_single_core_perf_test from the DPDK Test Suite
I had looked at the latest DTS repo from today:
git grep nic_single_core_perf_test
gives nothing.
Can you be more specific about exactly which *.py module from under "tests" folder is used ?
Regards,
Rami Rosen
[-- Attachment #2: Type: text/html, Size: 5324 bytes --]
next prev parent reply other threads:[~2019-01-08 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 10:45 Rami Rosen
2019-01-04 14:44 ` Jeremy Plsek
2019-01-04 15:33 ` Rami Rosen
2019-01-04 15:34 ` Thomas Monjalon
2019-01-04 16:15 ` Jeremy Plsek
2019-01-04 16:19 ` Thomas Monjalon
2019-01-08 6:40 ` Rami Rosen
2019-01-08 7:06 ` Tu, Lijuan [this message]
2019-01-08 8:23 ` Rami Rosen
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=8CE3E05A3F976642AAB0F4675D0AD20E0B9FE870@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=ci@dpdk.org \
--cc=jplsek@iol.unh.edu \
--cc=ramirose@gmail.com \
/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).