e1bf63afc9
For benchmarking purposes, we may want to use a relatively low queue depth but spread the operations across a wider range of memory. A new -a option is added where the user can specify an "allocate depth" to do exactly that. In this case, more tasks (and their associated buffers) can be allocated than we have actual queue depth. Then when we pick a new task for the next operation, it will use a different memory range and avoid always using the same buffers over and over again. If not specified, we just allocate the same number of tasks as the queue depth, which is the current behavior. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I78042d905fd49d130c4a318e2c19eb11b84ff726 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8451 Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Ziye Yang <ziye.yang@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot |
||
|---|---|---|
| .. | ||
| accel | ||
| bdev | ||
| blob | ||
| interrupt_tgt | ||
| ioat | ||
| nvme | ||
| nvmf | ||
| sock | ||
| util | ||
| vmd | ||
| Makefile | ||