On 26/04/2018 13:03, Ananyev, Konstantin wrote: [..]
I still think that if you'd like to extend rte_kvarrgs to be able to parse something like: "key=[val1,val2,...,valn]", you have to make it generic kvargs ability and put it into librte_kvargs, not try to introduce your own new parser here. Imagine that in addition to your 'port=[val1,val2, ..valn]' devargs string would contain some extra (let say device specific) parameters. What would happen, when PMD will try to use rte_kvargs_parse() on such string? My understanding - it would fail, correct?
This is partly dependent on what will (and won't) devargs provide when it is finalised. It was insourced in order to unblock the rest of the patchset in the meantime.
