Not to highjack this thread I created another one ? please have a look, thanks. http://dpdk.org/ml/archives/dev/2016-June/040079.html
Regards, Keith -----Original Message----- From: dev <dev-bounces at dpdk.org> on behalf of Thomas Monjalon <thomas.monja...@6wind.com> Date: Wednesday, June 1, 2016 at 9:03 AM To: Yuanhan Liu <yuanhan.liu at linux.intel.com> Cc: "dev at dpdk.org" <dev at dpdk.org>, Bruce Richardson <bruce.richardson at intel.com>, "Tan, Jianfeng" <jianfeng.tan at intel.com>, Stephen Hemminger <stephen at networkplumber.org>, Christian Ehrhardt <christian.ehrhardt at canonical.com>, Panu Matilainen <pmatilai at redhat.com>, Olivier Matz <olivier.matz at 6wind.com> Subject: Re: [dpdk-dev] [RFC] kernel paramters like DPDK CLI options >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 done in the application. >> > >> > > I'd say, that would work, but I see inflexibility and some drawbacks: >> > > >> > > - I would assume "--pciopt" has the input style of >> > > >> > > "domain:bus:devid:func,option1,option2,..." >> > > >> > > It then looks hard to me to use it: I need figure out the >> > > pci id first. >> > >> > What do you suggest instead of PCI id? >>
