From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47])
 by dpdk.org (Postfix) with ESMTP id 75F1D58D4
 for <dev@dpdk.org>; Thu,  2 Jun 2016 15:19:39 +0200 (CEST)
Received: by mail-wm0-f47.google.com with SMTP id a20so67117834wma.1
 for <dev@dpdk.org>; Thu, 02 Jun 2016 06:19:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=6wind-com.20150623.gappssmtp.com; s=20150623;
 h=from:to:cc:subject:date:message-id:user-agent:in-reply-to
 :references:mime-version:content-transfer-encoding;
 bh=kXweGxyTok1I7SMbWnYxRYjt0aM4IM/h+tBaGD+shB0=;
 b=oGfk8p9sa79GwYHLrUSn7GdFSNwxGZhe80+Ng4URpcwYvO/FgA1FrWgHBJ0IHQ7xkW
 oVybRESNBE5g8jyv2XtK4NkO7miyI8K3e+bISmO/MkCsXNrVHtwqjUQc8ZxHFKiZ7a/3
 nPOimMZNQg/eMjn3e5gVaaK2iLWqZKKufh2ho3g0jp6WfI4ui8XqF9LB7fznji8R5RjY
 tdoG57R1dvC5Vi96avNwQh9JgsV0cVAAIu3SnZ3YnX5D/JL6+ezqLzRB3qLiWQGXAzZz
 jtfMAt4SxiwXoJswZ40/ZfCiymotj0Nim7sbCP+QZMLP0B09Lvbn9NyzPHsqwm3CEqEA
 fFtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent
 :in-reply-to:references:mime-version:content-transfer-encoding;
 bh=kXweGxyTok1I7SMbWnYxRYjt0aM4IM/h+tBaGD+shB0=;
 b=iD8DVONTl4+CVp6IS5F3WFMXt6QrvAzyVthyIhKlRDcmtifFURCnUC3JUGpoZOlcV0
 QyUVFj0bImVzTSGw6MIp44ewVpg4//94SJ3RhdnI5F+t15q9ioeURuyz8SG8WkNsJAaV
 NUmqdFzM066000lNjH4g1LjbDUZc2ywbZvwyd9R5vTqd5nRaeA+ymzGuE6y/kWWWKDQZ
 TZFC8upvLMMgGGoPwgxSjeu/vHSHOFoeR4Lwb8IkGmSHGc1vcJp5NObDEgF21/oPZCuG
 EgqgQjxvpKSrJWEL9toTR/rT2suFV1YBM1dBkC5jIEFF6+qkqaJ9ecPDyCwJ0KyZNsyu
 6S1A==
X-Gm-Message-State: ALyK8tJoBqDsxiOHeiXBr7SOOJgZ3bD6pbaoUjPGAGC2qiIvEyn2e1d4MYnO2aGLU8ysTmaU
X-Received: by 10.194.141.238 with SMTP id rr14mr8588558wjb.58.1464873579298; 
 Thu, 02 Jun 2016 06:19:39 -0700 (PDT)
Received: from xps13.localnet ([2001:660:330f:38:7e7a:91ff:fe14:f0d2])
 by smtp.gmail.com with ESMTPSA id j9sm544276wju.46.2016.06.02.06.19.38
 (version=TLSv1/SSLv3 cipher=OTHER);
 Thu, 02 Jun 2016 06:19:38 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: "Wiles, Keith" <keith.wiles@intel.com>,
 Yuanhan Liu <yuanhan.liu@linux.intel.com>, dev@dpdk.org, "Richardson,
 Bruce" <bruce.richardson@intel.com>, "Tan, Jianfeng" <jianfeng.tan@intel.com>,
 Stephen Hemminger <stephen@networkplumber.org>,
 Christian Ehrhardt <christian.ehrhardt@canonical.com>,
 Panu Matilainen <pmatilai@redhat.com>, Olivier Matz <olivier.matz@6wind.com>
Date: Thu, 02 Jun 2016 15:19:37 +0200
Message-ID: <2363376.b1CWhBpcZG@xps13>
User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; )
In-Reply-To: <20160602104106.GA12923@hmsreliant.think-freely.org>
References: <C508AAA8-E813-4F2D-A2A4-1E2D5E34BF66@intel.com>
 <20160602104106.GA12923@hmsreliant.think-freely.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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 <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2016 13:19:39 -0000

2016-06-02 06:41, Neil Horman:
> I'm not sure why you're focusing no selecting a config file format at all.  Why
> not just focus on removing the argument parsing from the core rte_eal_init code,
> instead passing in a configuration struct that is stored and queried per
> application.  Leave the parsing of a config file and population of that config
> struct as an exercize to the application developer.  That way a given
> application can use command line options, config files, or whatever method they
> choose, which would be in keeping with traditional application design.
> 
> For the purposes of the example apps, it would seem that either JSON, YAML, or
> the above Lua format would work just fine.

+1