DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH RFC] usertools: add dpdk run script
Date: Fri, 14 Jul 2017 19:14:37 +0200	[thread overview]
Message-ID: <2044129.mseWKSvA0o@xps> (raw)
In-Reply-To: <4333988E-6D77-4DB1-B37A-1FD508EEB34F@intel.com>

14/07/2017 18:19, Wiles, Keith:
> > On Jul 6, 2017, at 4:37 PM, Keith Wiles <keith.wiles@intel.com> wrote:
> > 
> > I use a script like this one with pktgen and wanted to see if DPDK
> > would be interested in this application.
> > 
> > The following script adds support for executing applications using
> > a configuration file. The configuration file is formatted as a
> > python data file to be loaded by the run.py script.
> > 
> > Inside the configuration 'default.cfg' is the command line arguments
> > needed to execute the application. Any number of configuration  files
> > are allows for a single application for different execution. Normally
> > the configuration file can be in the application or example directory
> > or placed in a RTE_SDK/cfg directory.
> > 
> > The configuration file contains information about setup of the system
> > and how to run the application. The run.py script can setup the system
> > and/or execute the application with a simple command.
> > 
> > ./run.py -s default # for setup
> > ./run.py default # to execute the application.
> > 
> > I am not a great Python coder and any suggestions/patches would be great.
> 
> No comments on this RFC, should I submit a normal patch?

I have not reviewed the script.
I have just a comment about the scope of the project, as usual ;)
I am a bit worried about adding some application facilities
which may disturb library development focus of the project.

An open discussion would be useful on this topic,
so opinions (or +1/-1) are welcome!

      reply	other threads:[~2017-07-14 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 21:37 Keith Wiles
2017-07-14 16:19 ` Wiles, Keith
2017-07-14 17:14   ` Thomas Monjalon [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=2044129.mseWKSvA0o@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.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).