The rte_kvargs_process() was used to parse key-value (e.g. socket_id=0),
it also supports to parse only-key (e.g. socket_id). But many drivers's
callback can only handle key-value, it will segment fault if handles
only-key. so the patchset [1] was introduced.
Because the patchset [1] modified too much drivers, therefore:
1) A new API rte_kvargs_process_opt() was introduced, it inherits the
function of rte_kvargs_process() which could parse both key-value and
only-key.
2) Constraint the rte_kvargs_process() can only parse key-value.
This patchset also include one bugfix for kvargs of mvneta driver.
[1]
https://patches.dpdk.org/project/dpdk/patch/20230320092110.37295-1-fengcheng...@huawei.com/
Chengwen Feng (5):
kvargs: add one new process API
net/af_packet: use new API to parse kvargs
net/sfc: use new API to parse kvargs
net/tap: use new API to parse kvargs
net/mvneta: fix possible out-of-bounds write
drivers/common/sfc_efx/sfc_efx.c | 4 ++--
drivers/net/af_packet/rte_eth_af_packet.c | 4 ++--
drivers/net/mvneta/mvneta_ethdev.c | 3 +++
drivers/net/sfc/sfc_kvargs.c | 2 +-
drivers/net/tap/rte_eth_tap.c | 26 ++++++++++----------
lib/kvargs/rte_kvargs.c | 29 ++++++++++++++++++++++-
lib/kvargs/rte_kvargs.h | 28 ++++++++++++++++++++++
lib/kvargs/version.map | 3 +++
8 files changed, 80 insertions(+), 19 deletions(-)
--
2.17.1
