RE: [EXT] [PATCH] ipsec_mb: expect ENOTSUP in ipsec_mb_create()

["Ji, Kai" <kai.ji@intel.com>]

Is there any validation to this changes ? I Can't remember the exact reason why EEXIST
 returned, somehow we need to handle that case. 

Regards

Kai 

> -----Original Message-----
> From: Akhil Goyal <gakhil@marvell.com>
> Sent: Monday, February 27, 2023 6:27 PM
> To: Karas, Krzysztof <krzysztof.karas@intel.com>; Thomas Monjalon
> <thomas@monjalon.net>; Ji, Kai <kai.ji@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [EXT] [PATCH] ipsec_mb: expect ENOTSUP in ipsec_mb_create()
> 
> > Subject: [EXT] [PATCH] ipsec_mb: expect ENOTSUP in ipsec_mb_create()
> 
> Title should start with crypto/ipsec_mb:
> Avoid using function names in patch titles.
> 
> >
> > Commit b35848bc01f6 ("crypto/ipsec_mb: add multi-process IPC request
> > handler") is part of DPDK 22.11 release and it enforces usage of
> > shared config and multiprocess mode.
> >
> > DPDK is not required to be run with more than one process in general,
> > so instead of erroring out, catch the error and proceed with ipsec_mb
> > device creation normally.
> 
> This seems to be a fix, kindly adhere to the guidelines for fixes patches.
> >
> > Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
> 
> 
> Kai/Pablo,
> Acks please?
>