[0/2,v4] dm-crypt support for per-sector NVMe metadata

Message

Mikulas Patocka May 27, 2024, 3:39 p.m. UTC

Hi

Here I'm resending the dm-crypt support for per-sector NVMe metadata. I
made some changes to the first patch as suggested by Christoph Hellwig.

The first patch fixes a bug when splitting a bio with attached metadata.
The second patch enables dm-crypt to use NVMe metadata for authenticated
encryption. dm-crypt can run directly on NVMe without using dm-integrity.

These patches increase write throughput twice, because there is no write
to the dm-integrity journal.

An example how to use it (so far, there is no support in the userspace
cryptsetup tool):

# nvme format /dev/nvme1 -n 1 -lbaf=4
# dmsetup create cr --table '0 1048576 crypt
capi:authenc(hmac(sha256),cbc(aes))-essiv:sha256
01b11af6b55f76424fd53fb66667c301466b2eeaf0f39fd36d26e7fc4f52ade2de4228e996f5ae2fe817ce178e77079d28e4baaebffbcd3e16ae4f36ef217298
0 /dev/nvme1n1 0 2 integrity:32:aead sector_size:4096'

Mikulas

Comments

Jens Axboe June 26, 2024, 3:14 p.m. UTC | #1

On Mon, 27 May 2024 17:39:14 +0200, Mikulas Patocka wrote:
> Here I'm resending the dm-crypt support for per-sector NVMe metadata. I
> made some changes to the first patch as suggested by Christoph Hellwig.
> 
> The first patch fixes a bug when splitting a bio with attached metadata.
> The second patch enables dm-crypt to use NVMe metadata for authenticated
> encryption. dm-crypt can run directly on NVMe without using dm-integrity.
> 
> [...]

Applied, thanks!

[1/2] block: change rq_integrity_vec to respect the iterator
      commit: cf546dd289e0f6d2594c25e2fb4e19ee67c6d988

Best regards,