From 72ea6db37ae7d3adf99d9558e8d00da291d6edbb Mon Sep 17 00:00:00 2001 From: Konrad Sztyber Date: Thu, 29 Sep 2022 12:45:07 +0200 Subject: [PATCH] changelog: add a note about v22.09 changes in SMA Signed-off-by: Konrad Sztyber Change-Id: Ie998ae9e1a9a9a60bbe74bd388932dd3128b5564 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14749 Reviewed-by: Tomasz Zawadzki Reviewed-by: Ben Walker Tested-by: SPDK CI Jenkins --- CHANGELOG.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index a6041af3d..f1fa80729 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -111,6 +111,19 @@ Fixed hotplug when a device is inserted in a slot in which a disk was already en Added two new RPCs: `vmd_remove_device` simulating a hotremove, and `vmd_rescan`, which rescans all buses managed by the VMD driver and hotplugs all newfound devices. +### sma + +Extended `VolumeParameters` with crypto parameters allowing the user to configure crypto when +attaching a volume to a device. This interface is now supported by all upstream device types +(nvmf-tcp, virtio-blk, vfio-user) using `bdev_crypto`. Users must specify the crypto engine to use +under `crypto` section in config. It is also possible to register out-of-tree crypto engines by +inheriting from the `CryptoEngine` class. + +Added two new methods: `SetQos` and `GetQosCapabilities` allowing the user to configure QoS on a +per-device or per-volume level. Not all QoS settings have to be supported by each device, so users +can use `GetQosCapabilities` to query them for that. All upstream device types support QoS on a +per-volume level using bdev layer's QoS mechanism. + ## v22.05 ### sock