906c2adb86
When a device has resource-limitations such as the maximum-open-resources (mor) and this threshold is exceeded, then IO will fail upon completion. Such behavior is not the most user-friendly way to tell the user that they should provide a value for the fio-parameter 'max_open_zones'. This change provides an arguably more user-friendly approach by checking whether the device is limited and in case it is: * Provide a default value for 'max_open_zones', inform the user, and continue * Verify 'max_open_zones' and in case of error inform the user and return error Signed-off-by: Simon A. F. Lund <simon.lund@samsung.com> Change-Id: I76cb045d560b9ec5701d97b82a62947af11960b6 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4914 Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
|---|---|---|
| .. | ||
| abort | ||
| arbitration | ||
| cmb_copy | ||
| fio_plugin | ||
| hello_world | ||
| hotplug | ||
| identify | ||
| nvme_manage | ||
| perf | ||
| reconnect | ||
| Makefile | ||