From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: [RFC] Yet another option for DPDK options Date: Thu, 2 Jun 2016 15:56:46 +0800 Message-ID: <20160602075646.GT10038@yliu-dev.sh.intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Thomas Monjalon , "dev@dpdk.org" , "Richardson, Bruce" , "Tan, Jianfeng" , Stephen Hemminger , Christian Ehrhardt , Panu Matilainen , Olivier Matz , "Traynor, Kevin" To: "Wiles, Keith" 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) Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 direc= tion I was thinking was using a file for the options and configurations w= ith 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 file= s. 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 hie= rarchy 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 d= ata and not easy to make decisions about the system and applications at r= untime. __Just__ want to increase the chaos a bit, here is another option: YAML, which supports comments. >=20 > If the =E2=80=9Cdatabase=E2=80=9D of information could be queried by th= e EAL, drivers and application then we do not need to try and create a co= mplex command line. It would be nice to execute a DPDK applications like = this: >=20 > ./some_dpdk_app =E2=80=93config-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