From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: <dev@dpdk.org>, Anoob Joseph <anoobj@marvell.com>,
<bruce.richardson@intel.com>, <ciara.power@intel.com>,
<jerinj@marvell.com>, <fanzhang.oss@gmail.com>,
<arkadiuszx.kusztal@intel.com>, <kai.ji@intel.com>,
<jack.bond-preston@foss.arm.com>, <david.marchand@redhat.com>,
<hemant.agrawal@nxp.com>, <pablo.de.lara.guarch@intel.com>,
<fiona.trahe@intel.com>, <declan.doherty@intel.com>,
<matan@nvidia.com>, <ruifeng.wang@arm.com>,
<abhinandan.gujjar@intel.com>, <maxime.coquelin@redhat.com>,
<chenbox@nvidia.com>, <sunilprakashrao.uttarwar@amd.com>,
<andrew.boyer@amd.com>, <ajit.khaparde@broadcom.com>,
<raveendra.padasalagi@broadcom.com>, <vikas.gupta@broadcom.com>,
<zhangfei.gao@linaro.org>, <g.singh@nxp.com>,
<jianjay.zhou@huawei.com>, <lee.daly@intel.com>
Cc: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: [PATCH] doc: announce vhost changes to support asymmetric operation
Date: Mon, 22 Jul 2024 20:26:43 +0530 [thread overview]
Message-ID: <20240722145646.1219-1-gmuthukrishn@marvell.com> (raw)
Announce vhost ABI changes to modify few functions to support
asymmetric crypto operation.
Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
--
RFC:
https://patches.dpdk.org/project/dpdk/patch/20230928095300.1353-4-gmuthukrishn@marvell.com/
---
doc/guides/rel_notes/deprecation.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 6948641ff6..2f5c2c5a34 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -147,3 +147,10 @@ Deprecation Notices
will be deprecated and subsequently removed in DPDK 24.11 release.
Before this, the new port library API (functions rte_swx_port_*)
will gradually transition from experimental to stable status.
+
+* vhost: The function ``rte_vhost_crypto_create`` will accept a new parameter
+ to specify rte_mempool for asymmetric crypto session. The function
+ ``rte_vhost_crypto_finalize_requests`` will accept two new parameters,
+ where the first one is to specify vhost device id and other one is to specify
+ the virtio queue index. These two modifications are required to support
+ asymmetric crypto operation in vhost crypto and will break ABI.
--
2.21.0
next reply other threads:[~2024-07-22 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 14:56 Gowrishankar Muthukrishnan [this message]
2024-07-23 18:30 ` Jerin Jacob
2024-07-25 9:29 ` [EXTERNAL] " Gowrishankar Muthukrishnan
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=20240722145646.1219-1-gmuthukrishn@marvell.com \
--to=gmuthukrishn@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.boyer@amd.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=fiona.trahe@intel.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jack.bond-preston@foss.arm.com \
--cc=jerinj@marvell.com \
--cc=jianjay.zhou@huawei.com \
--cc=kai.ji@intel.com \
--cc=lee.daly@intel.com \
--cc=matan@nvidia.com \
--cc=maxime.coquelin@redhat.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=raveendra.padasalagi@broadcom.com \
--cc=ruifeng.wang@arm.com \
--cc=sunilprakashrao.uttarwar@amd.com \
--cc=vikas.gupta@broadcom.com \
--cc=zhangfei.gao@linaro.org \
/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).