Commit 173353ba authored by Chunyang Hui's avatar Chunyang Hui Committed by Jim Harris
Browse files

opal/Changelog: Add log for bdev opal 



Change-Id: Iae95c5961aac714cb28c9dbd09182cea1a339c03
Signed-off-by: default avatarChunyang Hui <chunyang.hui@intel.com>
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/471887


Reviewed-by: default avatarJim Harris <james.r.harris@intel.com>
Reviewed-by: default avatarTomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: default avatarShuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
parent fbe58225

CHANGELOG.md

+14 −0
Original line number Diff line number Diff line
@@ -9,6 +9,20 @@ Added new parameter `cdw0` to `spdk_bdev_io_complete_nvme_status()` and 
the NVMe completion queue DW0 entry. This allows vendor specific IO commands

to return commmand specific completion info back to the initiator.



### bdev opal



EXPERIMENTAL: A new opal bdev has been added to support management of

NVMe self-encrypting drives through the Opal specification. Users can

create opal bdevs from an NVMe namespace bdev, if the controller

containing that namespace supports Opal. Currently this is only

supported for namespace ID=1. The following RPCs have been added to

support Opal: `bdev_nvme_opal_init`, `bdev_nvme_opal_revert`,

`bdev_opal_create`, `bdev_opal_delete`, `bdev_opal_get_info`,

`bdev_opal_new_user`, `bdev_opal_set_lock_state`.

It does not yet support recreating the opal bdevs after application restart.

This bdev module should be considered very experimental, and the RPCs may

change significantly in future releases.



### bdev zone



Added new public header for zoned bdev. Zoned bdev is an extension