From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Anoob Joseph <anoobj@marvell.com>,
"radu.nicolau@intel.com" <radu.nicolau@intel.com>,
"declan.doherty@intel.com" <declan.doherty@intel.com>,
"matan@nvidia.com" <matan@nvidia.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
"asomalap@amd.com" <asomalap@amd.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
"jianjay.zhou@huawei.com" <jianjay.zhou@huawei.com>,
Gagandeep Singh <G.Singh@nxp.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH v2] doc: announce change in crypto raw data vector
Date: Sat, 07 Aug 2021 17:17:47 +0200 [thread overview]
Message-ID: <7945444.U02lEs5iZz@thomas> (raw)
In-Reply-To: <CO6PR18MB4484CBE3D55E7F2302206587D8F29@CO6PR18MB4484.namprd18.prod.outlook.com>
05/08/2021 16:04, Akhil Goyal:
> > The current crypto raw data vectors need to be extended to support
> > out of place processing. It is proposed to add additional desl_sgl
> > to provide details for destination sgl.
> > The same is also extended to support rte_security usecases, where
> > we need total data length to know how much additional memory space
> > is available in buffer other than data length so that driver/HW
> > can write expanded size data after encryption.
> >
> > Signed-off-by: Gagandeep Singh <G.Singh@nxp.com>
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> > ---
> > +* cryptodev: The structure ``rte_crypto_sym_vec`` would be updated to add
> > + ``dest_sgl`` to support out of place processing. This field will be null for
> > + inplace processing. This change is targeted for DPDK 21.11
> > +
> > +* cryptodev: The structure ``rte_crypto_vec`` would be updated to add
> > + ``tot_len`` to support total buffer length. This is required for security
> > + cases like IPsec and PDCP encryption offload to know how much additional
> > + memory space is available in buffer other than data length so that
> > driver/HW
> > + can write expanded size data after encryption. This change is targeted for
> > + DPDK 21.11
> > +
> Acked-by: Akhil Goyal <gakhil@marvell.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied, thanks.
next prev parent reply other threads:[~2021-08-07 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 8:05 [dpdk-dev] [PATCH] " Hemant Agrawal
2021-08-05 13:49 ` Zhang, Roy Fan
2021-08-05 13:52 ` Hemant Agrawal
2021-08-05 13:55 ` [dpdk-dev] [PATCH v2] " Hemant Agrawal
2021-08-05 14:04 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-08-07 15:17 ` Thomas Monjalon [this message]
2021-08-06 6:35 ` [dpdk-dev] " Hemant Agrawal
2021-08-06 10:04 ` Ananyev, Konstantin
2021-08-06 10:25 ` Hemant Agrawal
2021-08-06 10:38 ` Ananyev, Konstantin
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=7945444.U02lEs5iZz@thomas \
--to=thomas@monjalon.net \
--cc=G.Singh@nxp.com \
--cc=adwivedi@marvell.com \
--cc=ajit.khaparde@broadcom.com \
--cc=anoobj@marvell.com \
--cc=asomalap@amd.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jianjay.zhou@huawei.com \
--cc=konstantin.ananyev@intel.com \
--cc=matan@nvidia.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=ruifeng.wang@arm.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).