Spdk/test/vhost/common/fio_jobs/default_initiator.job

[global]
thread=1
group_reporting=1
direct=1
time_based=1
do_verify=1
verify=md5
verify_backlog=1024
fsync_on_close=1
iodepth=32
[job0]
test/vhost: Fio tests for vhost initiator. Change-Id: Iad11eef12c0f7f80c26264f65a38df798eae1a27 Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-on: https://review.gerrithub.io/378071 Reviewed-by: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> 2017-09-12 13:47:30 +00:00			`[global]`
			`thread=1`
			`group_reporting=1`
			`direct=1`
			`time_based=1`
			`do_verify=1`
			`verify=md5`
			`verify_backlog=1024`
fio_jobs: add fsync_on_close to fio args This is to help facilitate the update of the fio_ubuntu binary to fio-3.3 Change-Id: I4c896dc60255f821a5cf66af818396f210304f07 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/395394 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> 2018-01-18 22:23:26 +00:00			`fsync_on_close=1`
test/vhost: test multiple connections to a single vhost device Two fio instancess will try to do simultaneous I/O to a single vhost block device. The test uses default_initiator.job as a fio config, which apparently wasn't used anywhere and had to be slightly adjusted to work. Specificaly, we had to specify an empty job in the config file, as specifying it from the command line wouldn't make it inherit any options from the [global] section in the file. Change-Id: I2c2a96a709c567f5c910715a5b3d85a4e28bcb97 Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/419066 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> 2018-07-12 14:22:17 +00:00			`iodepth=32`
			`[job0]`