ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

changelog: add a note about v22.09 changes in SMA

Browse Source 
Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com>
Change-Id: Ie998ae9e1a9a9a60bbe74bd388932dd3128b5564
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14749
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
This commit is contained in:
Konrad Sztyber 2022-09-29 12:45:07 +02:00 committed by Tomasz Zawadzki
parent cdffb29760
commit 72ea6db37a
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
CHANGELOG.md
View File

@ -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