CHANGELOG: Fix the wrong location for NVMe-oF target section

Merge nvmf section into NVMe-oF target section.

Change-Id: I0279392e655b719ff6229b00838fcc6406265113
Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/451787
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
This commit is contained in:
Shuhei Matsumoto 2019-04-24 07:49:19 +09:00 committed by Jim Harris
parent 47cf47e482
commit 31158c0dd0

View File

@ -61,6 +61,9 @@ The size of a shared receive queue is defined by transport configuration file pa
`MaxSRQDepth` and `nvmf_create_transport` RPC method parameter `max_srq_depth`.
Default size is 4096.
Add model number as parameter to construct_nvmf_subsystem (-d option),
rather than using hardcoded define.
### env
The `phys_addr` parameter in spdk_malloc() and spdk_zmalloc() has been deprecated.
@ -91,11 +94,6 @@ is specified, use that specified nbd device. If it's not specified, pick availab
Add Opal scan support for NVMe to check whether it supports SED Opal and dump
device info. nvme_manage tool can be used to invoke this.
### nvmf
Add model number as parameter to construct_nvmf_subsystem (-d option),
rather than using hardcoded define.
## v19.01:
### ocf bdev