From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Power, Ciara" <ciara.power@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Ji, Kai" <kai.ji@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] crypto/ipsec_mb: fix getting process ID per job
Date: Thu, 23 Nov 2023 17:10:52 +0000 [thread overview]
Message-ID: <DM8PR11MB5591439D9C95B5915BEA732884B9A@DM8PR11MB5591.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231123170701.901946-1-ciara.power@intel.com>
> -----Original Message-----
> From: Power, Ciara <ciara.power@intel.com>
> Sent: Thursday, November 23, 2023 5:07 PM
> To: dev@dpdk.org
> Cc: thomas@monjalon.net; Ji, Kai <kai.ji@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Power, Ciara <ciara.power@intel.com>;
> stable@dpdk.org
> Subject: [PATCH] crypto/ipsec_mb: fix getting process ID per job
>
> 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, instead of per job.
>
> Fixes: 9593d83e5d88 ("crypto/ipsec_mb: fix aesni_mb multi-process session
> ID")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com"
next prev parent reply other threads:[~2023-11-23 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 17:07 Ciara Power
2023-11-23 17:10 ` De Lara Guarch, Pablo [this message]
2023-11-23 17:11 ` Ji, Kai
2023-11-23 17:15 ` [PATCH v2] " Ciara Power
2023-11-23 17:22 ` Ji, Kai
2023-11-23 17:26 ` De Lara Guarch, Pablo
2023-11-24 9:55 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM8PR11MB5591439D9C95B5915BEA732884B9A@DM8PR11MB5591.namprd11.prod.outlook.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).