[dpdk-dev] [PATCH 2/2] eal: add eal_parse_optionlist to parse user input
David Marchand
david.marchand at redhat.com
Wed Jan 29 18:44:43 CET 2020
On Tue, Jan 28, 2020 at 6:35 PM Ferruh Yigit <ferruh.yigit at intel.com> wrote:
> On 1/27/2020 10:30 AM, Hariprasad Govindharajan wrote:
> > In current version, there is a function which parses
> > the corelist based on user value. A new generic
> > function eal_parse_optionlist is added which will
> > parse corelist as well as similar user input so
> > that we can use it as a public API too.
> >
> > Signed-off-by: Hariprasad Govindharajan <hariprasad.govindharajan at intel.com>
>
> Hi David,
>
> Overall this patchset is to add '--portlist' command to testpmd and remove
> existing 64 port limitation.
>
> And in this patch re-uses the exiting parser function in eal and converts it to
> API, question is if eal is good place to have this API, what do you think about it?
Exporting string parsers from the EAL has little value.
Ok we avoid code duplication (and I can see other places in the tree
where it might be used), but in the end we will have to maintain this
API in the ABI when it enters the stable ABI.
I am for avoiding this.
--
David Marchand
More information about the dev
mailing list