From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 2C3603DC for ; Fri, 3 Mar 2017 11:53:20 +0100 (CET) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga104.jf.intel.com with ESMTP; 03 Mar 2017 02:53:19 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,236,1484035200"; d="scan'208";a="71772176" Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by fmsmga005.fm.intel.com with ESMTP; 03 Mar 2017 02:53:18 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.173]) by IRSMSX107.ger.corp.intel.com ([169.254.10.3]) with mapi id 14.03.0248.002; Fri, 3 Mar 2017 10:53:16 +0000 From: "Dumitrescu, Cristian" To: "Legacy, Allain (Wind River)" , "Richardson, Bruce" CC: "dev@dpdk.org" , "Jolliffe, Ian (Wind River)" Thread-Topic: [PATCH 3/5] cfgfile: add support for unamed global section Thread-Index: AQHSk4tgVL/PsqOiw0GykXDainBcKKGC8QNQ 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> In-Reply-To: <1488482971-170522-4-git-send-email-allain.legacy@windriver.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTE3ZTE4M2UtYTNkYi00YmU4LTlkMGMtNzBmMGQxNTdlYWM0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjIuMTEuMCIsIlRydXN0ZWRMYWJlbEhhc2giOiJPY0VzR2g1WUV2TGs3QkRQODlnXC8xQXpjUHhETk9QaE9IK2QxWE9Kek52dz0ifQ== x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 3/5] cfgfile: add support for unamed global section X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 10:53:20 -0000 > -----Original Message----- > From: Allain Legacy [mailto:allain.legacy@windriver.com] > Sent: Thursday, March 2, 2017 7:29 PM > To: Richardson, Bruce ; Dumitrescu, Cristian > > Cc: dev@dpdk.org; Jolliffe, Ian (Wind River) > 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?