From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Ji, Kai" <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: RE: [dpdk-dev v4] crypto/ipsec_mb: multi-process IPC request handler
Date: Wed, 26 Oct 2022 12:32:16 +0000 [thread overview]
Message-ID: <DM8PR11MB5591188FC2A4AC79A5CECC6484309@DM8PR11MB5591.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221026102731.16683-1-kai.ji@intel.com>
Hi Kai,
A couple of minor bits left.
> -----Original Message-----
> From: Ji, Kai <kai.ji@intel.com>
> Sent: Wednesday, October 26, 2022 11:28 AM
> To: dev@dpdk.org
> Cc: gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Burakov, Anatoly
> <anatoly.burakov@intel.com>
> Subject: [dpdk-dev v4] crypto/ipsec_mb: multi-process IPC request handler
>
> As the queue pair used in secondary process need to be setuped by the
needs/needed to be set up by...
> primary process, this patch add an IPC register function to help secondary
This patch adds
> process to send out queue-pair setup reguest to primary process via IPC
request
> messages. A new "qp_in_used_pid" param stores the PID to provide the
> ownership of the queue-pair so that only the PID matched queue-pair can be
> free'd in the request.
>
> Signed-off-by: Kai Ji <kai.ji@intel.com>
> --- a/drivers/crypto/ipsec_mb/ipsec_mb_private.h
> +++ b/drivers/crypto/ipsec_mb/ipsec_mb_private.h
> @@ -25,6 +25,9 @@
> /* Maximum length for memzone name */
> #define IPSEC_MB_MAX_MZ_NAME 32
>
> +/* ipsec mb multi-process queue pair config */ #define
> IPSEC_MB_MP_MSG
> +"ipsec_mb_mp_msg"
> +
> enum ipsec_mb_vector_mode {
> IPSEC_MB_NOT_SUPPORTED = 0,
> IPSEC_MB_SSE,
> @@ -142,18 +145,49 @@ struct ipsec_mb_qp {
> enum ipsec_mb_pmd_types pmd_type;
> /**< pmd type */
> uint8_t digest_idx;
> + /**< The process id used for queue pairs **/
> + uint16_t qp_used_by_pid;
> /**< Index of the next
> * slot to be used in temp_digests,
> * to store the digest for a given operation
> */
Comments are mixed here (digest_idx and qp_used_by_pid).
> IMB_MGR *mb_mgr;
> - /* Multi buffer manager */
> + /**< Multi buffer manager */
> const struct rte_memzone *mb_mgr_mz;
> - /* Shared memzone for storing mb_mgr */
> + /**< Shared memzone for storing mb_mgr */
> __extension__ uint8_t additional_data[];
> /**< Storing PMD specific additional data */ };
>
next prev parent reply other threads:[~2022-10-26 12:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 23:51 [dpdk-dev v1] " Kai Ji
2022-10-24 23:38 ` [dpdk-dev v2] " Kai Ji
2022-10-25 21:48 ` [dpdk-dev v3] " Kai Ji
2022-10-26 8:17 ` De Lara Guarch, Pablo
2022-10-26 10:01 ` [dpdk-dev v4] " Kai Ji
2022-10-26 10:22 ` Kai Ji
2022-10-26 10:27 ` Kai Ji
2022-10-26 11:07 ` Kusztal, ArkadiuszX
2022-10-26 12:32 ` De Lara Guarch, Pablo [this message]
2022-10-26 12:48 ` Kai Ji
2022-10-26 13:04 ` De Lara Guarch, Pablo
2022-10-26 13:19 ` [dpdk-dev v5] " Kai Ji
2022-10-27 9:54 ` [EXT] " Akhil Goyal
2022-10-27 17:57 ` Konstantin Ananyev
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=DM8PR11MB5591188FC2A4AC79A5CECC6484309@DM8PR11MB5591.namprd11.prod.outlook.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
/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).