DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Allain Legacy <allain.legacy@windriver.com>
Cc: dev@dpdk.org, jingjing.wu@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/2] testpmd load cmdline commands from file
Date: Mon, 01 May 2017 16:08:48 +0200	[thread overview]
Message-ID: <3653279.UaGtptcWdd@xps> (raw)
In-Reply-To: <20170331191320.143047-1-allain.legacy@windriver.com>

31/03/2017 21:13, Allain Legacy:
> Enhancing test-pmd to be able to load CLI commands from file both at
> runtime and at startup.  Usually the number of commands to run is small
> enough that a simple cut-n-paste does the trick, but while testing the flow
> API it was necessary to load several hundred commands and cut-n-paste could
> not keep up.
> 
> I started with adding support to load the commands at startup
> (--cmdline-file=/home/ubuntu/somefile.txt), but then realized that I needed
> to remove/re-add commands at runtime so I added CLI commands to take care
> of that aspect as well ("testpmd> load /home/ubuntu/somefile.txt")
> 
> I thought of removing the startup command support since the same could be
> accomplished by using the new "load" command once the process starts up,
> but then I realized that it may be useful for someone using non-interactive
> mode.
> 
> I am open to the idea of squashing both commits together if necessary.
> 
> 
> Allain Legacy (2):
>   app/testpmd: load cmdline commands on startup
>   app/testpmd: load cmdline commands at runtime

Applied, thanks

      parent reply	other threads:[~2017-05-01 14:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 19:13 Allain Legacy
2017-03-31 19:13 ` [dpdk-dev] [PATCH 1/2] app/testpmd: load cmdline commands from file at startup Allain Legacy
2017-04-25  9:43   ` Wu, Jingjing
2017-03-31 19:13 ` [dpdk-dev] [PATCH 2/2] app/testpmd: load cmdline commands from file at runtime Allain Legacy
2017-04-25  9:47   ` Wu, Jingjing
2017-05-01 14:08 ` 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=3653279.UaGtptcWdd@xps \
    --to=thomas@monjalon.net \
    --cc=allain.legacy@windriver.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@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).