From: Bart Van Assche <bvanassche@acm.org>
To: Israel Rukshin <israelr@nvidia.com>, dm-devel <dm-devel@redhat.com>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>,
Eric Biggers <ebiggers@kernel.org>,
Nitzan Carmi <nitzanc@nvidia.com>
Subject: Re: [dm-devel] [RFC PATCH 0/1] Add inline encryption support for dm-crypt
Date: Thu, 13 Jan 2022 13:22:03 -0800 [thread overview]
Message-ID: <8f2a832f-06de-d269-a24b-cce933a296f9@acm.org> (raw)
In-Reply-To: <1642097341-6521-1-git-send-email-israelr@nvidia.com>
On 1/13/22 10:09, Israel Rukshin wrote:
> I am working to add support for inline encryption/decryption
> at storage protocols like nvmf over RDMA. The HW that I am
> working with is ConnecX-6 Dx, which supports inline crypto
> and can send the data on the fabric at the same time.
>
> This patchset is based on v5.16-rc4 with Eric Biggers patches
> of the HW wrapped keys.
> It can be retrieved from branch "wip-wrapped-keys" at
> https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git
>
> I tested this patch with modified nvme-rdma as the block device
> and created a DM crypt on top of it. I got performance enhancement
> compared to SW crypto. I tested the HW wrapped inline mode with
> the HW and the standard mode with a fallback algorithm.
Hi Israel,
Thank you for your work. For future patches related to inline
encryption, please Cc Eric Biggers.
Thanks,
Bart.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2022-01-13 21:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 18:09 [dm-devel] [RFC PATCH 0/1] Add inline encryption support for dm-crypt Israel Rukshin
2022-01-13 18:09 ` [dm-devel] [PATCH 1/1] dm crypt: Add inline encryption support Israel Rukshin
2022-01-14 8:06 ` Damien Le Moal
2022-01-14 8:14 ` Damien Le Moal
2022-01-16 10:29 ` Israel Rukshin
2022-01-13 21:22 ` Bart Van Assche [this message]
2022-01-14 20:51 ` [dm-devel] [RFC PATCH 0/1] Add inline encryption support for dm-crypt Milan Broz
2022-01-14 22:27 ` Eric Biggers
2022-01-15 9:22 ` Milan Broz
2022-01-18 19:38 ` Eric Biggers
2022-01-19 5:18 ` Christoph Hellwig
2022-01-17 7:52 ` Christoph Hellwig
2022-01-17 10:50 ` Milan Broz
2022-01-17 14:00 ` Israel Rukshin
2022-01-18 16:45 ` Christoph Hellwig
2022-01-18 20:27 ` Eric Biggers
2022-01-19 5:15 ` Christoph Hellwig
2022-01-14 22:49 ` Eric Biggers
2022-01-16 10:15 ` Israel Rukshin
2022-01-18 20:02 ` Eric Biggers
2022-01-19 15:45 ` Israel Rukshin
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=8f2a832f-06de-d269-a24b-cce933a296f9@acm.org \
--to=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=ebiggers@kernel.org \
--cc=israelr@nvidia.com \
--cc=mgurtovoy@nvidia.com \
--cc=nitzanc@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.