From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 0/2] testpmd load cmdline commands from file Date: Mon, 01 May 2017 16:08:48 +0200 Message-ID: <3653279.UaGtptcWdd@xps> References: <20170331191320.143047-1-allain.legacy@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, jingjing.wu@intel.com To: Allain Legacy Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 218122A62 for ; Mon, 1 May 2017 16:08:52 +0200 (CEST) In-Reply-To: <20170331191320.143047-1-allain.legacy@windriver.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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