From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>,
Anoob Joseph <anoobj@marvell.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"ciara.power@intel.com" <ciara.power@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
"fanzhang.oss@gmail.com" <fanzhang.oss@gmail.com>,
"Ji, Kai" <kai.ji@intel.com>,
"jack.bond-preston@foss.arm.com" <jack.bond-preston@foss.arm.com>,
"Marchand, David" <david.marchand@redhat.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"matan@nvidia.com" <matan@nvidia.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>,
"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"chenbox@nvidia.com" <chenbox@nvidia.com>,
"sunilprakashrao.uttarwar@amd.com"
<sunilprakashrao.uttarwar@amd.com>,
"andrew.boyer@amd.com" <andrew.boyer@amd.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"raveendra.padasalagi@broadcom.com"
<raveendra.padasalagi@broadcom.com>,
"vikas.gupta@broadcom.com" <vikas.gupta@broadcom.com>,
"zhangfei.gao@linaro.org" <zhangfei.gao@linaro.org>,
"g.singh@nxp.com" <g.singh@nxp.com>,
"jianjay.zhou@huawei.com" <jianjay.zhou@huawei.com>,
"Daly, Lee" <lee.daly@intel.com>
Subject: RE: [PATCH] doc: announce cryptodev changes to offload RSA in VirtIO
Date: Sun, 18 Aug 2024 04:36:44 +0000 [thread overview]
Message-ID: <CO1PR18MB47149BBA0B3ECD3ABF283D96CB832@CO1PR18MB4714.namprd18.prod.outlook.com> (raw)
In-Reply-To: <PH0PR11MB501352254A788BF2A3C111CB9FB82@PH0PR11MB5013.namprd11.prod.outlook.com>
Hi Arek,
> I do not have any particular security issues in mind here, and if PMD need to
> copy keys internally, for alignment or padding purposes, redundancy problems
> can be overcome. My concern was, that it is the more natural way of handling
> the API; we have one key, multiple padding schemes, so we reflect this logic in
> the API.
>
> Both options are widely used; libcrypto, for example is setting padding within
> session, other languages like Go, Rust are setting it as an argument to the
> method of the key struct.
>
> If this is that problematic with VirtIO compatibility, I say this change is okay.
>
Thank you for your input. I understand your concern. We ensure the impact
Is nominal and make changes if needed.
Thanks,
next prev parent reply other threads:[~2024-08-18 4:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 14:55 Gowrishankar Muthukrishnan
2024-07-24 5:10 ` Anoob Joseph
2024-07-24 6:49 ` [EXTERNAL] " Akhil Goyal
2024-07-25 9:48 ` Kusztal, ArkadiuszX
2024-07-25 15:53 ` Gowrishankar Muthukrishnan
2024-07-30 14:39 ` Gowrishankar Muthukrishnan
2024-07-31 12:51 ` Thomas Monjalon
2024-07-31 14:26 ` Thomas Monjalon
2024-08-07 13:31 ` Kusztal, ArkadiuszX
2024-08-18 4:36 ` Gowrishankar Muthukrishnan [this message]
2024-07-25 16:00 ` 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=CO1PR18MB47149BBA0B3ECD3ABF283D96CB832@CO1PR18MB4714.namprd18.prod.outlook.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=thomas@monjalon.net \
--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).