Commit 72ea6db3 authored by Konrad Sztyber's avatar Konrad Sztyber Committed by Tomasz Zawadzki
Browse files

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



Signed-off-by: default avatarKonrad Sztyber <konrad.sztyber@intel.com>
Change-Id: Ie998ae9e1a9a9a60bbe74bd388932dd3128b5564
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/14749


Reviewed-by: default avatarTomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: default avatarBen Walker <benjamin.walker@intel.com>
Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
parent cdffb297

CHANGELOG.md

+13 −0
Original line number Diff line number Diff line
@@ -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