From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: <dev@dpdk.org>
Cc: <anoobj@marvell.com>, Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>, Kai Ji <kai.ji@intel.com>,
Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>,
Jay Zhou <jianjay.zhou@huawei.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: [RFC 0/6] vhost: add asymmetric crypto support
Date: Thu, 28 Sep 2023 15:22:54 +0530 [thread overview]
Message-ID: <20230928095300.1353-1-gmuthukrishn@marvell.com> (raw)
This series of patches add asymmetric crypto support in vhost library
and virtio PMD. Only RSA algorithm is enabled as a first step.
To verify functionality in QEMU, you would need:
https://github.com/qemu/qemu/commit/5c33f9783ace0b5e077060b220978d94fecb3e81
There is VirtIO specification change proposed for RSA support, and this
series apply it at required places.
https://lists.oasis-open.org/archives/virtio-comment/202305/msg00341.html
In case, qemu crashes, check disabling VHOST_USER_PROTOCOL_F_CONFIG in
virtio pmd, when the device starts. This issue was seen with older qemu
but I'll check a bit closer.
Gowrishankar Muthukrishnan (6):
cryptodev: move RSA padding information into xform
cryptodev: fix RSA xform for ASN.1 syntax
vhost: add asymmetric RSA support
crypto/virtio: add asymmetric RSA support
examples/vhost_crypto: add asymmetric support
app/test: add asymmetric tests for virtio pmd
app/test/test_cryptodev_asym.c | 40 +-
app/test/test_cryptodev_rsa_test_vectors.h | 28 +
drivers/common/cpt/cpt_ucode_asym.h | 4 +-
drivers/crypto/cnxk/cnxk_ae.h | 13 +-
drivers/crypto/octeontx/otx_cryptodev_ops.c | 4 +-
drivers/crypto/openssl/openssl_pmd_private.h | 1 +
drivers/crypto/openssl/rte_openssl_pmd.c | 4 +-
drivers/crypto/openssl/rte_openssl_pmd_ops.c | 1 +
drivers/crypto/qat/qat_asym.c | 17 +-
.../virtio/virtio_crypto_capabilities.h | 19 +
drivers/crypto/virtio/virtio_cryptodev.c | 388 ++++++++++--
drivers/crypto/virtio/virtio_rxtx.c | 233 +++++++-
examples/fips_validation/main.c | 52 +-
examples/vhost_crypto/main.c | 50 +-
lib/cryptodev/cryptodev_pmd.h | 6 +
lib/cryptodev/rte_crypto_asym.h | 8 +-
lib/vhost/rte_vhost_crypto.h | 14 +-
lib/vhost/vhost.c | 11 +-
lib/vhost/vhost.h | 1 +
lib/vhost/vhost_crypto.c | 551 ++++++++++++++++--
lib/vhost/vhost_user.c | 4 +
lib/vhost/vhost_user.h | 34 +-
lib/vhost/virtio_crypto.h | 87 ++-
23 files changed, 1375 insertions(+), 195 deletions(-)
--
2.25.1
next reply other threads:[~2023-09-28 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 9:52 Gowrishankar Muthukrishnan [this message]
2023-09-28 9:52 ` [RFC 1/6] cryptodev: move RSA padding information into xform Gowrishankar Muthukrishnan
2023-09-28 9:52 ` [RFC 2/6] cryptodev: fix RSA xform for ASN.1 syntax Gowrishankar Muthukrishnan
2023-09-28 9:52 ` [RFC 3/6] vhost: add asymmetric RSA support Gowrishankar Muthukrishnan
2023-09-28 9:52 ` [RFC 4/6] crypto/virtio: " Gowrishankar Muthukrishnan
2023-09-28 9:52 ` [RFC 5/6] examples/vhost_crypto: add asymmetric support Gowrishankar Muthukrishnan
2023-09-28 9:53 ` [RFC 6/6] app/test: add asymmetric tests for virtio pmd 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=20230928095300.1353-1-gmuthukrishn@marvell.com \
--to=gmuthukrishn@marvell.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=jianjay.zhou@huawei.com \
--cc=kai.ji@intel.com \
--cc=maxime.coquelin@redhat.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).