From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <cristian.dumitrescu@intel.com> Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id B0B5AD072; Tue, 28 Mar 2017 12:20:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1490696459; x=1522232459; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=0wr6+Tw01o64Lc+1V4XKTTsfKPL2WXFo2B9apomvHcA=; b=jD1Sv49CmOcI/Y3pn18n3tmHYF12egR8iwn22b26ni3uPDHVLV63DZAI OrRmDMfMIjdgZc62K6zDBFMz9H9BCQ==; Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Mar 2017 03:20:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,236,1486454400"; d="scan'208";a="65912711" Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by orsmga002.jf.intel.com with ESMTP; 28 Mar 2017 03:20:55 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.239]) by IRSMSX107.ger.corp.intel.com ([169.254.10.107]) with mapi id 14.03.0319.002; Tue, 28 Mar 2017 11:20:54 +0100 From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com> To: Thomas Monjalon <thomas.monjalon@6wind.com> CC: "Richardson, Bruce" <bruce.richardson@intel.com>, "Legacy, Allain (Wind River)" <allain.legacy@windriver.com>, "dev@dpdk.org" <dev@dpdk.org>, "yuanhan.liu@linux.intel.com" <yuanhan.liu@linux.intel.com>, "techboard@dpdk.org" <techboard@dpdk.org> Thread-Topic: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements Thread-Index: AQHSmNarI1I75TdkvkC/5qQNqNb7E6Gp+HYAgAANngCAAAEpgIAABUYAgAATb3D///U2AIAAEWJg Date: Tue, 28 Mar 2017 10:20:53 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912652780046@IRSMSX108.ger.corp.intel.com> References: <1488482971-170522-1-git-send-email-allain.legacy@windriver.com> <22590962.V8IQgtpKlO@xps13> <3EB4FA525960D640B5BDFFD6A3D891265277FF85@IRSMSX108.ger.corp.intel.com> <82821129.A9hgLN2u53@xps13> In-Reply-To: <82821129.A9hgLN2u53@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZDM4MjBiMzctMjI0NC00N2ZhLWFjZjMtYjIwMzdmYjE2YjJkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IkxUMkRYdlJkQjlDdUdpYkhSanFQS2dIQWt2SWRmR3lrakJNMzltZU5qZ1U9In0= 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 v2 0/6] librte_cfgfile enhancements X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list 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> X-List-Received-Date: Tue, 28 Mar 2017 10:20:59 -0000 > > This library is an important utility for applications, similar to librt= e_cmdline > and others. I think it is not fair from your side to refer to librte_cfgf= ile without > any reference to librte_cmdline. >=20 > I agree Cristian. > I was just writing another email about removing librte_cmdline: > http://dpdk.org/ml/archives/dev/2017-March/061777.html > This thread was about librte_cfgfile. I hope you'll agree I am really fai= r :) >=20 > It is really a scope question and should be managed by the techboard (CC)= . >=20 It is virtually impossible to write a non-trivial packet processing applica= tion without support for configuration file (librte_cfgfile) and CLI (librt= e_cmdline), therefore I think both of these building blocks are definitely = within the scope of DPDK. As its name suggests, DPDK is a *development kit*= for data plane applications, right?