From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [PATCH 3/5] cfgfile: add support for unamed global
	section
Date: Fri, 3 Mar 2017 10:53:16 +0000
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912652758055@IRSMSX108.ger.corp.intel.com>
References: <1488482971-170522-1-git-send-email-allain.legacy@windriver.com>
 <1488482971-170522-4-git-send-email-allain.legacy@windriver.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Jolliffe, Ian (Wind River)"
 <ian.jolliffe@windriver.com>
To: "Legacy, Allain (Wind River)" <allain.legacy@windriver.com>, "Richardson,
 Bruce" <bruce.richardson@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga06.intel.com (mga06.intel.com [134.134.136.31])
 by dpdk.org (Postfix) with ESMTP id 2C3603DC
 for <dev@dpdk.org>; Fri,  3 Mar 2017 11:53:20 +0100 (CET)
In-Reply-To: <1488482971-170522-4-git-send-email-allain.legacy@windriver.com>
Content-Language: en-US
List-Id: DPDK patches and discussions <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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>



> -----Original Message-----
> From: Allain Legacy [mailto:allain.legacy@windriver.com]
> Sent: Thursday, March 2, 2017 7:29 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org; Jolliffe, Ian (Wind River) <ian.jolliffe@windriver.com>
> Subject: [PATCH 3/5] cfgfile: add support for unamed global section
>=20
> The current implementation of the cfgfile library requires that all
> key=3Dvalue pairs be within [SECTION] definitions.  The ini file standard
> allows for key=3Dvalue pairs in an unnamed section.  That section is
> considered the [GLOBAL] section.
>=20
> This commit adds the capability of parsing key=3Dvalue pairs from such an
> unnamed section. The CFG_FLAG_GLOBAL_SECTION flag must be passed to
> the
> rte_cfgfile_load() API to enable this functionality.
>=20

What is the motivation for the having key/value pair outside of any section=
? What would be the drawback of having the user explicitly define a GLOBAL =
section to host these key/value pairs?