Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Bruce Richardson
On Tue, Mar 28, 2017 at 05:41:01PM +0200, Thomas Monjalon wrote: > 2017-03-28 16:24, Bruce Richardson: > > On Tue, Mar 28, 2017 at 12:12:26PM +0200, Thomas Monjalon wrote: > > > 2017-03-28 09:58, Dumitrescu, Cristian: > > > > > > As follow-up to my own mail, for this specific library example, I > >

Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Thomas Monjalon
2017-03-28 16:24, Bruce Richardson: > On Tue, Mar 28, 2017 at 12:12:26PM +0200, Thomas Monjalon wrote: > > 2017-03-28 09:58, Dumitrescu, Cristian: > > > > > As follow-up to my own mail, for this specific library example, I > > > > > wouldn't look to remove it from DPDK anyway. Parsing ini files is

Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Bruce Richardson
On Tue, Mar 28, 2017 at 12:12:26PM +0200, Thomas Monjalon wrote: > 2017-03-28 09:58, Dumitrescu, Cristian: > > > > As follow-up to my own mail, for this specific library example, I > > > > wouldn't look to remove it from DPDK anyway. Parsing ini files is fairly > > > > trivial, so I think it's not

Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Dumitrescu, Cristian
> > This library is an important utility for applications, similar to > > librte_cmdline > and others. I think it is not fair from your side to refer to librte_cfgfile > without > any reference to librte_cmdline. > > I agree Cristian. > I was just writing another email about removing librte_cmd

Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Thomas Monjalon
2017-03-28 09:58, Dumitrescu, Cristian: > > > As follow-up to my own mail, for this specific library example, I > > > wouldn't look to remove it from DPDK anyway. Parsing ini files is fairly > > > trivial, so I think it's not a big deal to keep our own version and not > > > have an external depende

Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Dumitrescu, Cristian
> > As follow-up to my own mail, for this specific library example, I > > wouldn't look to remove it from DPDK anyway. Parsing ini files is fairly > > trivial, so I think it's not a big deal to keep our own version and not > > have an external dependency - especially since it's already there and no

Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Thomas Monjalon
2017-03-28 10:22, Bruce Richardson: > On Tue, Mar 28, 2017 at 10:18:28AM +0100, Bruce Richardson wrote: > > On Tue, Mar 28, 2017 at 10:29:44AM +0200, Thomas Monjalon wrote: > > > 2017-03-09 08:10, Allain Legacy: > > > > This patchset includes some minor enhancements that we have developped > > > >

Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Bruce Richardson
On Tue, Mar 28, 2017 at 10:18:28AM +0100, Bruce Richardson wrote: > On Tue, Mar 28, 2017 at 10:29:44AM +0200, Thomas Monjalon wrote: > > 2017-03-09 08:10, Allain Legacy: > > > This patchset includes some minor enhancements that we have developped for > > > our DPDK application. We would like to co

Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Bruce Richardson
On Tue, Mar 28, 2017 at 10:29:44AM +0200, Thomas Monjalon wrote: > 2017-03-09 08:10, Allain Legacy: > > This patchset includes some minor enhancements that we have developped for > > our DPDK application. We would like to contribute them upstream to help > > ease adoption of the DPDK by anyone loo

Re: [dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-28 Thread Thomas Monjalon
2017-03-09 08:10, Allain Legacy: > This patchset includes some minor enhancements that we have developped for > our DPDK application. We would like to contribute them upstream to help > ease adoption of the DPDK by anyone looking for this type of > functionality. The commit logs on each patch sho

[dpdk-dev] [PATCH v2 0/6] librte_cfgfile enhancements

2017-03-09 Thread Allain Legacy
This patchset includes some minor enhancements that we have developped for our DPDK application. We would like to contribute them upstream to help ease adoption of the DPDK by anyone looking for this type of functionality. The commit logs on each patch should be self-sufficient in explaining the