DPDK CI discussions
 help / color / Atom feed
From: Rami Rosen <ramirose@gmail.com>
To: Jeremy Plsek <jplsek@iol.unh.edu>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] Question about performance test
Date: Tue, 8 Jan 2019 08:40:27 +0200
Message-ID: <CAHLOa7Q-_dpa7992URAy7UotQwyaqV=Dz3gdGTNVR2H6qmd+hA@mail.gmail.com> (raw)
In-Reply-To: <CA+xUZB66fvJtTpqL=6U2gkZ2B6P6q60iNCKoZNq5WA7LYYm1dA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

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: 625 bytes --]

<div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hi Jeremy,</div><div>&gt;At the moment, we only run performance tests. Specifically the nic_single_core_perf_test from the DPDK Test Suite </div><div><br></div><div>I had looked at the latest DTS repo from today:<br></div><div><br></div><div>git grep nic_single_core_perf_test</div><div>gives nothing.<br></div><div><br></div><div>Can you be more specific about exactly which *.py module from under &quot;tests&quot; folder is used ?</div><div><br></div><div>Regards,</div><div>Rami Rosen</div></div></div><br><div class="gmail_quote"><div dir="ltr"><br></div></div></div>

  parent reply index

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 [this message]
2019-01-08  7:06     ` Tu, Lijuan
2019-01-08  8:23       ` Rami Rosen

Reply instructions:

You may reply publically 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='CAHLOa7Q-_dpa7992URAy7UotQwyaqV=Dz3gdGTNVR2H6qmd+hA@mail.gmail.com' \
    --to=ramirose@gmail.com \
    --cc=ci@dpdk.org \
    --cc=jplsek@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

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox