From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>,
Victor Kaplansky <vkaplans@redhat.com>
Cc: dev@dpdk.org, jingjing.wu@intel.com,
"Amnon Ilan" <ailan@redhat.com>,
"Tim Irnich" <tim.irnich@ericsson.com>,
"Georg Kunz" <georg.kunz@ericsson.com>,
"Gabor Halász" <gabor.halasz@ericsson.com>,
"Mechthild Buescher" <mechthild.buescher@ericsson.com>
Subject: Re: [dpdk-dev] [RFC PATCH 0/4] testpmd: simulating noisy host environment
Date: Thu, 09 Nov 2017 22:13:46 +0100 [thread overview]
Message-ID: <2833194.20UaxZ7Ebt@xps> (raw)
In-Reply-To: <20171031101352.GB10572@bricha3-MOBL3.ger.corp.intel.com>
31/10/2017 11:13, Bruce Richardson:
> On Mon, Oct 30, 2017 at 02:41:05AM -0400, Victor Kaplansky wrote:
> >
> > This RFC patch propose enhancements to testpmd to simulate
> > more realistic behavior of a guest machine engaged in receiving
> > and sending packets performing Virtual Network Function (VNF).
> >
> > The goal is to enable simple of measuring performance impact on cache and
> > memory footprint utilization from various VNF co-located on the
> > same host machine.
> >
> > This series of patches adds the new command line switches to
> > testpmd:
> >
> Hi,
>
> while I think this functionality is of use, I don't think it should go
> into testpmd. Testpmd is designed for testing NIC PMDs, and not as a
> general test tool, and is already complicated enough with lots of
> commandline options. For the task of testing VNF use-cases, I think a
> new separate app or example would be better.
Not sure.
If we need to mix the VNF simulation options with the NIC features
options (implemented in testpmd), then testpmd would be a good fit.
Please Victor, give your arguments to make the discussion progressing.
next prev parent reply other threads:[~2017-11-09 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 6:41 Victor Kaplansky
2017-10-31 10:13 ` Bruce Richardson
2017-11-09 21:13 ` Thomas Monjalon [this message]
2017-11-13 9:41 ` Victor Kaplansky
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=2833194.20UaxZ7Ebt@xps \
--to=thomas@monjalon.net \
--cc=ailan@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gabor.halasz@ericsson.com \
--cc=georg.kunz@ericsson.com \
--cc=jingjing.wu@intel.com \
--cc=mechthild.buescher@ericsson.com \
--cc=tim.irnich@ericsson.com \
--cc=vkaplans@redhat.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).