From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 2C079377E for ; Thu, 2 Jun 2016 09:56:51 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga102.fm.intel.com with ESMTP; 02 Jun 2016 00:56:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,405,1459839600"; d="scan'208";a="967278652" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by orsmga001.jf.intel.com with ESMTP; 02 Jun 2016 00:56:42 -0700 Date: Thu, 2 Jun 2016 15:56:46 +0800 From: Yuanhan Liu To: "Wiles, Keith" Cc: Thomas Monjalon , "dev@dpdk.org" , "Richardson, Bruce" , "Tan, Jianfeng" , Stephen Hemminger , Christian Ehrhardt , Panu Matilainen , Olivier Matz , "Traynor, Kevin" Message-ID: <20160602075646.GT10038@yliu-dev.sh.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [RFC] Yet another option for DPDK options X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2016 07:56:51 -0000 On Wed, Jun 01, 2016 at 03:00:11PM +0000, Wiles, Keith wrote: > I have been looking at a number of different options here and the direction I was thinking was using a file for the options and configurations with the data in a clean format. It should be helpful and handy for productive usage. But for development and debugging, I'd say CLI options is more convenient and flexible. I would be more willing to fiddle with CLI options than editing config files. In another word, +1, but I would also assume that we will keep the CLI options. > It could have been a INI file or JSON or XML, but they all seem to have some problems I do not like. The INI file is too flat and I wanted a hierarchy in the data, the JSON data is similar and XML is just hard to read. I wanted to be able to manage multiple applications and possible system the DPDK/app runs. The problem with the above formats is they are just data and not easy to make decisions about the system and applications at runtime. __Just__ want to increase the chaos a bit, here is another option: YAML, which supports comments. > > If the “database” of information could be queried by the EAL, drivers and application then we do not need to try and create a complex command line. It would be nice to execute a DPDK applications like this: > > ./some_dpdk_app –config-file dpdk-config-filename It could be simpler if you hardcode a default config file, say /etc/dpdk.conf. I'm thinking OVS guys would be happy to see that? :) --yliu