[dpdk-dev] [RFC] kernel paramters like DPDK CLI options

2016-06-02 Thread Yuanhan Liu
On Wed, Jun 01, 2016 at 04:03:07PM +0200, Thomas Monjalon wrote: > 2016-06-01 21:19, Yuanhan Liu: > > On Wed, Jun 01, 2016 at 02:39:28PM +0200, Thomas Monjalon wrote: > > > I was thinking to implement the library options parsing in DPDK. > > > But if the application implements its own options

[dpdk-dev] [RFC] kernel paramters like DPDK CLI options

2016-06-01 Thread Yuanhan Liu
On Wed, Jun 01, 2016 at 02:39:28PM +0200, Thomas Monjalon wrote: > I was thinking to implement the library options parsing in DPDK. > But if the application implements its own options parsing without using > the DPDK one, yes the option parsing is obviously done in the application. > > > I'd say,

[dpdk-dev] [RFC] kernel paramters like DPDK CLI options

2016-06-01 Thread Yuanhan Liu
On Wed, Jun 01, 2016 at 12:17:50PM +0200, Thomas Monjalon wrote: > Hi, > > 2016-06-01 14:04, Yuanhan Liu: > > Hi all, > > > > I guess we (maybe just me :) have stated few times something like > > "hey, this kind of stuff is good to have, but you are trying to > > add an EAL CLI option for a

[dpdk-dev] [RFC] kernel paramters like DPDK CLI options

2016-06-01 Thread Yerden Zhumabekov
I recently felt tired enough of specifying various options for EAL, so I came up to use ini-based configuration. EAL parameters from dedicated section of ini file are parsed to argv array which is subsequently fed to rte_eal_init(). Quite handy, but maybe a little overkill. On 01.06.2016

[dpdk-dev] [RFC] kernel paramters like DPDK CLI options

2016-06-01 Thread Thomas Monjalon
2016-06-01 21:19, Yuanhan Liu: > On Wed, Jun 01, 2016 at 02:39:28PM +0200, Thomas Monjalon wrote: > > I was thinking to implement the library options parsing in DPDK. > > But if the application implements its own options parsing without using > > the DPDK one, yes the option parsing is obviously

[dpdk-dev] [RFC] kernel paramters like DPDK CLI options

2016-06-01 Thread Wiles, Keith
:03 AM To: Yuanhan Liu Cc: "dev at dpdk.org" , Bruce Richardson , "Tan, Jianfeng" , Stephen Hemminger , Christian Ehrhardt , Panu Matilainen , Olivier Matz Subject: Re: [dpdk-dev] [RFC] kernel paramters like DPDK CLI options >2016-06-01 21:19, Yuanhan Liu: >> On Wed, Jun 0

[dpdk-dev] [RFC] kernel paramters like DPDK CLI options

2016-06-01 Thread Thomas Monjalon
2016-06-01 19:40, Yuanhan Liu: > On Wed, Jun 01, 2016 at 12:17:50PM +0200, Thomas Monjalon wrote: > > 2016-06-01 14:04, Yuanhan Liu: > > > Apparently, adding a new EAL option like "--force-legacy" looks > > > wrong. > > > > > > The generic yet elegant solution I just thought of while having > > >

[dpdk-dev] [RFC] kernel paramters like DPDK CLI options

2016-06-01 Thread Yuanhan Liu
Hi all, I guess we (maybe just me :) have stated few times something like "hey, this kind of stuff is good to have, but you are trying to add an EAL CLI option for a specific subsystem/driver, which is wrong". One recent example that is still fresh in my mind is the one from Christian [0], that

[dpdk-dev] [RFC] kernel paramters like DPDK CLI options

2016-06-01 Thread Thomas Monjalon
Hi, 2016-06-01 14:04, Yuanhan Liu: > Hi all, > > I guess we (maybe just me :) have stated few times something like > "hey, this kind of stuff is good to have, but you are trying to > add an EAL CLI option for a specific subsystem/driver, which is > wrong". Yes > One recent example that is