From: Akhil Goyal <gakhil@marvell.com>
To: Kai Ji <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: RE: [EXT] [dpdk-dev v5] crypto/ipsec_mb: multi-process IPC request handler
Date: Thu, 27 Oct 2022 09:54:48 +0000 [thread overview]
Message-ID: <CO6PR18MB4484E976C017371182722086D8339@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221026131902.31884-1-kai.ji@intel.com>
> As the queue pair used in secondary process needs to be set up by
> the primary process, this patch adds an IPC register function to help
> secondary process to send out queue-pair setup request 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>
> Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
> v5:
> - minor updates and typo fix
Applied to dpdk-next-crypto
Thanks.
next prev parent reply other threads:[~2022-10-27 9:54 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
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 ` Akhil Goyal [this message]
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=CO6PR18MB4484E976C017371182722086D8339@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@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).