From: Srujana Challa <schalla@marvell.com>
To: <virtio-comment@lists.linux.dev>
Cc: <mst@redhat.com>, <cohuck@redhat.com>, <mvaralar@redhat.com>,
<parav@nvidia.com>, <sburla@marvell.com>,
<ndabilpuram@marvell.com>, <jerinj@marvell.com>,
<anoobj@marvell.com>, <schalla@marvell.com>
Subject: [PATCH RFC v3 0/4] introduce IPsec Service in virtio-crypto
Date: Wed, 22 Jan 2025 11:46:40 +0530 [thread overview]
Message-ID: <20250122061644.266560-1-schalla@marvell.com> (raw)
This series enhances virtio-crypto by adding support for IPsec
services. These patches aim to extend the capabilities of virtio-crypto,
enabling it to handle IPsec operations efficiently. In addition
to standard crypto processing, the IPsec protocol processing is
also offloaded to the Crypto device as lookaside operation.
It utilizes new virtio basic facilities, including capability and
resource objects. Below is a summary of the changes introduced:
Patch1:
This patch introduces the foundational support for IPsec services within
the virtio-crypto framework, outlining the necessary capabilities for
IPsec operations.
Patch2:
This patch adds resource objects required for programming IPsec Security
Associations (SAs) for both encryption and decryption processes.
Patch3:
This patch includes new opcodes specific to IPsec operations,
facilitating the handling of IPsec data requests within the
virtio-crypto driver.
Patch4:
This patch specifies the requirements for both the device and the driver
to support IPsec operations.
These enhancements are for providing support for IPsec within the
virtio-crypto device/driver, improving security and performance for
virtualized environments. We believe these additions will significantly
benefit users who rely on virtio-crypto for secure data transmission.
v2:
- Addressed the review comments from Matias.
v3:
- Addressed the review comments from Parav Pandit.
Srujana Challa (4):
virtio-crypto: Add IPsec service operation and Capabilities
virtio-crypto: Add resource objects for IPsec outbound and inbound SAs
virtio-crypto: Add new IPsec opcodes to data request
virtio-crypto: Add device and driver requirements for IPsec operation
device-types/crypto/description.tex | 486 ++++++++++++++++++++-
device-types/crypto/device-conformance.tex | 1 +
device-types/crypto/driver-conformance.tex | 1 +
introduction.tex | 12 +
4 files changed, 495 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2025-01-22 6:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 6:16 Srujana Challa [this message]
2025-01-22 6:16 ` [PATCH RFC v3 1/4] virtio-crypto: Add IPsec service operation and Capabilities Srujana Challa
2025-02-10 19:46 ` Parav Pandit
2025-02-13 12:55 ` Sebastian Mauritsson
2025-02-13 17:34 ` Srujana Challa
2025-01-22 6:16 ` [PATCH RFC v3 2/4] virtio-crypto: Add resource objects for IPsec outbound and inbound SAs Srujana Challa
2025-02-10 19:46 ` Parav Pandit
2025-02-13 13:09 ` Sebastian Mauritsson
2025-02-13 14:35 ` Srujana Challa
2025-02-15 18:35 ` Parav Pandit
2025-02-17 5:40 ` Srujana Challa
2025-01-22 6:16 ` [PATCH RFC v3 3/4] virtio-crypto: Add new IPsec opcodes to data request Srujana Challa
2025-02-10 19:46 ` Parav Pandit
2025-01-22 6:16 ` [PATCH RFC v3 4/4] virtio-crypto: Add device and driver requirements for IPsec operation Srujana Challa
2025-02-10 19:47 ` Parav Pandit
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=20250122061644.266560-1-schalla@marvell.com \
--to=schalla@marvell.com \
--cc=anoobj@marvell.com \
--cc=cohuck@redhat.com \
--cc=jerinj@marvell.com \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=ndabilpuram@marvell.com \
--cc=parav@nvidia.com \
--cc=sburla@marvell.com \
--cc=virtio-comment@lists.linux.dev \
/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