f69367c788
All jobs are created at boot, meaning the setup callback is invoked for all jobs before any are executed. But it may be useful to put 'stonewall' parameters in the job file to execute a bunch of workloads in succession, starting one workload when the previous one completes. But since qpairs are created currently during setup, the total number of workloads that can be expressed is limited since qpairs for all workloads are allocated up front. So instead defer allocation of the io qpairs until the file_open callback. These don't get called until the job associated with the 'file' (in this case, the nvme namespace) is ready to execute. Note that we cannot free the qpairs in the file_close callback, since fio may 'close' the file before all I/O have been completed. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I3c60cf27c3660a3c94042c0de719f5bebdb9b417 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/7481 Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: <dongx.yi@intel.com> Community-CI: Broadcom CI Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
|---|---|---|
| .. | ||
| abort | ||
| arbitration | ||
| cmb_copy | ||
| fio_plugin | ||
| hello_world | ||
| hotplug | ||
| identify | ||
| nvme_manage | ||
| perf | ||
| reconnect | ||
| Makefile | ||