Re: [PATCH v2] crypto/ipsec_mb: fix getting process ID per job

2023-11-24 Thread Thomas Monjalon
> > Currently, when using IPsec-mb 1.4+, the process ID is obtained for each > > job in > > a burst with a call to getpid(). > > This system call uses too many CPU cycles, and is unnecessary per job. > > > > Instead, set the process ID value per lcore. > > This is read when processing the burst,

RE: [PATCH v2] crypto/ipsec_mb: fix getting process ID per job

2023-11-23 Thread De Lara Guarch, Pablo
> -Original Message- > From: Power, Ciara > Sent: Thursday, November 23, 2023 5:16 PM > To: dev@dpdk.org > Cc: tho...@monjalon.net; Ji, Kai ; De Lara Guarch, Pablo > ; Power, Ciara ; > sta...@dpdk.org > Subject: [PATCH v2] crypto/ipsec_mb: fix getting process ID per job > > Currently,

Re: [PATCH v2] crypto/ipsec_mb: fix getting process ID per job

2023-11-23 Thread Ji, Kai
Acked-by: Kai Ji From: Power, Ciara Sent: 23 November 2023 17:15 To: dev@dpdk.org Cc: tho...@monjalon.net ; Ji, Kai ; De Lara Guarch, Pablo ; Power, Ciara ; sta...@dpdk.org Subject: [PATCH v2] crypto/ipsec_mb: fix getting process ID per job Currently, when