Vincent Fu [Wed, 2 Aug 2023 16:30:17 +0000 (12:30 -0400)]
t/fiotestlib: make recorded command prettier
Instead of recording fio test commands as a single very long line, put
each option on its own line to make the command easier for humans to
digest.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 2 Aug 2023 16:23:37 +0000 (12:23 -0400)]
t/nvmept: fix typo
Make the filenames for the nvmept artifacts start with nvmept instead
of readonly.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Jens Axboe [Mon, 31 Jul 2023 21:03:37 +0000 (15:03 -0600)]
Merge branch 'master' of https://github.com/min22/fio
* 'master' of https://github.com/min22/fio:
iolog.c: fix inaccurate clat when replay trace
Jens Axboe [Mon, 31 Jul 2023 21:03:03 +0000 (15:03 -0600)]
Merge branch 'improment/constness' of https://github.com/dpronin/fio
* 'improment/constness' of https://github.com/dpronin/fio:
use 'const' where it is required
Denis Pronin [Sun, 30 Jul 2023 22:29:04 +0000 (01:29 +0300)]
use 'const' where it is required
protect variables and parameters from programmer's point of view with
'constness'
Signed-off-by: Denis Pronin <dannftk@yandex.ru>
Jens Axboe [Fri, 28 Jul 2023 17:32:22 +0000 (11:32 -0600)]
Revert "correctly free thread_data options at the topmost parent process"
This reverts commit
913028e97ceedcf2cf1ec6ec32228b3c50e7337c.
This commit is causing the static analyzers to freak out, and also
crashes on Windows. Revert it for now.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Jens Axboe [Fri, 28 Jul 2023 15:11:15 +0000 (09:11 -0600)]
Merge branch 'td-eo-double-free-fix' of https://github.com/dpronin/fio
* 'td-eo-double-free-fix' of https://github.com/dpronin/fio:
correctly free thread_data options at the topmost parent process
Jens Axboe [Fri, 28 Jul 2023 15:11:01 +0000 (09:11 -0600)]
Merge branch 'master' of https://github.com/dpronin/fio
* 'master' of https://github.com/dpronin/fio:
fix missing headers in multiple files
Jens Axboe [Fri, 28 Jul 2023 15:10:44 +0000 (09:10 -0600)]
Merge branch 'io_uring' of https://github.com/dpronin/fio
* 'io_uring' of https://github.com/dpronin/fio:
io_uring engine: 'atomic_load_relaxed' instead of 'atomic_load_acquire'
Denis Pronin [Fri, 28 Jul 2023 14:25:06 +0000 (17:25 +0300)]
io_uring engine: 'atomic_load_relaxed' instead of 'atomic_load_acquire'
motivation here is that we do not have here any explicit READ dependency
on atomic load because actually we just need in these places only
operation to perform atomically without any explicit barriers given by
memory model
Signed-off-by: Denis Pronin <dannftk@yandex.ru>
Denis Pronin [Thu, 27 Jul 2023 22:26:22 +0000 (01:26 +0300)]
correctly free thread_data options at the topmost parent process
for non-threaded mode: since thread_data::eo is a pointer within shared
memory between the topmost fio parent process and its children let the
fio parent process set the pointer to NULL as just it frees its copy of
'eo' as memory previously allocated by means of 'malloc' meaning that
each child and the parent process itself must free it
for threaded mode we leave it as it has always been
also we do not need to check td->io_ops for being able to free td->eo in
fio_options_free()
Signed-off-by: Denis Pronin <dannftk@yandex.ru>
Denis Pronin [Fri, 28 Jul 2023 09:39:58 +0000 (12:39 +0300)]
fix missing headers in multiple files
some files require to have some missing headers included
Signed-off-by: Denis Pronin <dannftk@yandex.ru>
Jens Axboe [Thu, 27 Jul 2023 19:48:26 +0000 (13:48 -0600)]
Merge branch 'helper_thread-fix-missing-stdbool-header' of https://github.com/dpronin/fio
* 'helper_thread-fix-missing-stdbool-header' of https://github.com/dpronin/fio:
helper_thread.h: forwardly declare structures fio_sem and sk_out
helper_thread.h: include missing stdbool.h because 'bool' type is used
Denis Pronin [Thu, 27 Jul 2023 19:08:45 +0000 (22:08 +0300)]
helper_thread.h: forwardly declare structures fio_sem and sk_out
helper_thread_create() function requires two structures to be declared
Signed-off-by: Denis Pronin <dannftk@yandex.ru>
Denis Pronin [Thu, 27 Jul 2023 19:06:59 +0000 (22:06 +0300)]
helper_thread.h: include missing stdbool.h because 'bool' type is used
missing headers should be included at the places where they are
certainly used
Signed-off-by: Denis Pronin <dannftk@yandex.ru>
Jens Axboe [Thu, 27 Jul 2023 19:11:01 +0000 (13:11 -0600)]
Merge branch 'diskutil-fix-missing-headers' of https://github.com/dpronin/fio
* 'diskutil-fix-missing-headers' of https://github.com/dpronin/fio:
diskutil.h: fix missing headers wanted by the header
Denis Pronin [Thu, 27 Jul 2023 18:49:31 +0000 (21:49 +0300)]
diskutil.h: fix missing headers wanted by the header
diskutil.h requires 3 more headers to fulfill several types therein
without having to rely on headers hopefully included before this one
Signed-off-by: Denis Pronin <dannftk@yandex.ru>
Kookoo Gu [Wed, 26 Jul 2023 04:48:35 +0000 (12:48 +0800)]
iolog.c: fix inaccurate clat when replay trace
When do timestamp replay with high qd it will only reap the
completed commands when the qd reach the max iodepth, the commands
probably are finished long ago before command completion handling.
Fix is to use io_u_queued_complete instead of just usec_sleep in
iolog_delay
Signed-off-by: Kookoo Gu <Zhimin.Gu@solidigm.com>
Jens Axboe [Fri, 21 Jul 2023 21:23:40 +0000 (15:23 -0600)]
Merge branch 'prio-hints'
* prio-hints:
stats: Add hint information to per priority level stats
cmdprio: Add support for per I/O priority hint
options: add priohint option
os-linux: add initial support for IO priority hints
cmdprio: Introduce generic option definitions
os-linux: Cleanup IO priority class and value macros
Damien Le Moal [Fri, 21 Jul 2023 11:05:10 +0000 (20:05 +0900)]
stats: Add hint information to per priority level stats
Modify the json and standard per-priority output stats to display the
hint value together with the priority class and level.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230721110510.44772-7-dlemoal@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Damien Le Moal [Fri, 21 Jul 2023 11:05:09 +0000 (20:05 +0900)]
cmdprio: Add support for per I/O priority hint
Introduce the new option cmdprio_hint to allow specifying I/O priority
hints per IO with the io_uring and libaio IO engines. A third acceptable
format for the cmdprio_bssplit option is also introduced to allow
specifying an I/O hint in addition to a priority class and level.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230721110510.44772-6-dlemoal@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Damien Le Moal [Fri, 21 Jul 2023 11:05:08 +0000 (20:05 +0900)]
options: add priohint option
Introduce the new option priohint to allow users to specify an I/O
priority hint applying to all IOs issued by a job. This increases fio
server version (FIO_SERVER_VER) to 101.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230721110510.44772-5-dlemoal@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Damien Le Moal [Fri, 21 Jul 2023 11:05:07 +0000 (20:05 +0900)]
os-linux: add initial support for IO priority hints
Add initial support for Linux to allow specifying a hint for any
priority value. With this change, a priority value becomes the
combination of a priority class, a priority level and a hint.
The generic os.h ioprio manipulation macros, as well as the
os-dragonfly.h ioprio manipulation macros are modified to ignore this
hint.
For all other OSes that do not support priority classes, priotity hints
are ignored and always equal to 0.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230721110510.44772-4-dlemoal@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Damien Le Moal [Fri, 21 Jul 2023 11:05:06 +0000 (20:05 +0900)]
cmdprio: Introduce generic option definitions
The definition of the per-I/O priority options for the io_uring and
libaio I/O engines are almost identical, differing only by the option
group and option data structure used.
Introduce the CMDPRIO_OPTIONS macro in engines/cmdprio.h to generically
define these options in the io_uring and libaio engines to simplify the
code.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230721110510.44772-3-dlemoal@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Damien Le Moal [Fri, 21 Jul 2023 11:05:05 +0000 (20:05 +0900)]
os-linux: Cleanup IO priority class and value macros
In os/os-linux.h, define the ioprio() macro using the already defined
IOPRIO_MAX_PRIO macro instead of hard coding the maximum priority value
again. Also move the definitions of the ioprio_class() and ioprio()
macros before the ioprio_value() function and use ioprio_class() inside
ioprio_value_is_class_rt() instead of re-coding the iopriority class
extraction again in that function.
Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230721110510.44772-2-dlemoal@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Shin'ichiro Kawasaki [Fri, 21 Jul 2023 04:44:44 +0000 (13:44 +0900)]
backend: clear IO_U_F_FLIGHT flag in zero byte read path
When read io_u completes with zero byte read, it sets EIO as the error
and put the io_u. However, it does not clear the IO_U_F_FLIGHT flag.
When fio runs with --ignore_error=EIO option, the io_u with the flag is
reused for next I/O and causes an assertion failure:
fio: ioengines.c:335: td_io_queue: Assertion `(io_u->flags & IO_U_F_FLIGHT) == 0' failed.
The failure is observed with blktests test case block/011 which runs fio
with the --ignore_error=EIO option [1].
[1] https://github.com/osandov/blktests/issues/29
Fix this by calling clear_io_u() instead of put_io_u() in the zero byte
read path. clear_io_u() clears the IO_U_F_FLIGHT flag then calls
put_io_u().
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230721044444.749537-1-shinichiro.kawasaki@wdc.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Dmitry Fomichev [Wed, 19 Jul 2023 10:57:56 +0000 (19:57 +0900)]
t/zbd: add max_active configs to run-tests-against-nullb
Introduce several new test device configurations to cover the cases with
max_active_zones is not being zero, i.e. limited. Two group of new
configurations are added, one with max_active_zones == max_open_zones
and the other with max_active_zones > max_open_zones.
Signed-off-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-14-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Dmitry Fomichev [Wed, 19 Jul 2023 10:57:55 +0000 (19:57 +0900)]
t/zbd: fix null_blk configuration in run-tests-against-nullb
Correctly set max_open in null_blk configfs.
Fix displayed number of conventional zones in section config banner.
Signed-off-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-13-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:54 +0000 (19:57 +0900)]
t/zbd: add missing prep_write for test cases with write workloads
The test cases from 54 to 57 do writes but miss prep_write() call which
resets zones of the test target device with max_active_zones limit. This
results in failures due to open zones out of I/O ranges and
max_active_zones limit error. Add the missing prep_write() call to avoid
the failures.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-12-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:53 +0000 (19:57 +0900)]
t/zbd: fix fio failure check and SG node failure in test case 31
The test case 31 runs fio twice but the failure of the first fio run was
not checked. This allowed the test case pass even with wrong
max_open_zones value. To fix this, check exit code of the fio run.
Also, the first fio run fails when the test target devices are SG nodes,
since libzbc I/O engine is not used. To fix this, call the ioengine()
helper function which adjusts I/O engine for each device.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-11-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:52 +0000 (19:57 +0900)]
t/zbd: get max_open_zones from sysfs
The helper bash function gets max_open_zones limit of the test target
device using sg_inq and libzbc tools. This works for SAS/SATA devices
but does not work for ZNS or null_blk devices. This results is running
the test case 31 with wrong max_open_zones value. Fix this by referring
max_open_zones sysfs attribute.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-10-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:51 +0000 (19:57 +0900)]
t/zbd: add test case to check max_active_zones limit error message
The recent fio change introduced a new error message to indicate
max_active_zones limit error of zoned block devices. Add a test case to
check the error message is reported.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-9-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:50 +0000 (19:57 +0900)]
t/zbd: add test case to check zones in closed condition
When the zoned block device has max_active_zones limit, the zones in
open or closed condition consume resource on the device. If the number
of zones in open or closed condition gets larger than the
max_active_zones limit, the device reports an error. Until the recent
fix ("zbd: write to closed zones on the devices with max_active_zones
limit"), fio handled only zones in open condition as write target then
fio was not able to avoid the error.
Add a test which confirms that the fix avoids the error by handling
zones in closed condition as write target. This test case requires the
device has max_active_zones limit. Prepare zones in closed condition as
many as the max_active_zones limit. Do random write and check no error.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-8-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:49 +0000 (19:57 +0900)]
t/zbd: add max_active_zone variable
To test fio behavior on zoned block devices with max_active_zones limit,
add a global variable which holds the limit value. Also add helper
functions to check max_active_zones limit of the test target devices and
max_active_zones requirement of test cases.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-7-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:48 +0000 (19:57 +0900)]
t/zbd: add close_zone helper function
Add a helper function which sets the specified zone in closed condition.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-6-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:47 +0000 (19:57 +0900)]
docs: modify max_open_zones option description
A recent commit modified the max_open_zones option to improve handling
of zoned block devices with max_active_zones limit. Modify description
of the option to meet the change.
For that purpose, explain the relation between the max_open_zones option
and the device side limits max_active_zones and max_open_zones. Also
mention about three zone conditions 'implicit open', 'explict open' and
'closed'. And replace the word 'zone state' with 'zone condition'.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-5-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:46 +0000 (19:57 +0900)]
zbd: print max_active_zones limit error message
When zoned block devices have max_active_zones limit and when write
operations exceed that limit, Linux block sub-system reports EOVERFLOW.
However, the strerror() string for EOVERFLOW does not mention about
max_active_zones then it confuses users.
To avoid the confusion, print additional error message to indicate the
max_active_zones limit. For this purpose, add a hook function
zbd_log_err() and call it from __io_u_log_error().
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-4-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:45 +0000 (19:57 +0900)]
zbd: write to closed zones on the devices with max_active_zones limit
Current fio implementation does not handle zones in closed condition as
write target zones. When the device has max_active_zones limit, the
write to other zones may cause errors by exceeding the limit, since the
zones in closed condition consume the device resource for the
max_active_zones limit.
To avoid the error, handle the zones in closed condition as write target
in same manner as the zones in open condition when the device has the
max_active_zones limit. At the job start, check each condition of the
zones in the IO ranges and if it has closed condition, pass the zone
to zbd_write_zones_get() in same manner as the zones in open condition.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-3-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Wed, 19 Jul 2023 10:57:44 +0000 (19:57 +0900)]
zbd: get max_active_zones limit value from zoned devices
As a preparation to improve open zones accounting for devices with the
max_active_zones limit, get the limit from the devices. In same manner
as max_open_zones, call get_max_active_zones callback if the I/O engine
supports it. Add the new call back to the I/O engine API and bump up
FIO_IOOPS_VERSION. It is expected that io_uring and xnvme engines to
support the callback later. When the callback is not available, refer
max_active_zones sysfs attribute for block devices. When the limit value
is not available, use zero value which means no limit. Keep the obtained
limit value in the struct zoned_block_device_info.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Link: https://lore.kernel.org/r/20230719105756.553146-2-shinichiro.kawasaki@wdc.com
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Jens Axboe [Sat, 15 Jul 2023 15:57:43 +0000 (09:57 -0600)]
Merge branch 'patch-3' of https://github.com/yangjueji/fio
* 'patch-3' of https://github.com/yangjueji/fio:
fix: io_uring sqpoll issue_time empty when kernel not yet read sq
Michael Kelley [Fri, 14 Jul 2023 17:06:01 +0000 (17:06 +0000)]
thinktime: Avoid calculating a negative time left to wait
When the thinktime_spin option specifies a value that is within
a few milliseconds of the thinktime value, in handle_thinktime()
it's possible in a VM environment for the duration of usec_spin()
to exceed the thinktime value. While doing usec_spin(), the vCPU
could get de-scheduled or the hypervisor could steal CPU time
from the vCPU. When the guest vCPU runs after being scheduled
again, it may read the clock and find that more time has elapsed
than intended. In such a case, the time left to wait could be
calculated as a negative value. Subsequent calculations then go
awry because the time left is cast as unsigned.
Fix this by detecting when the time left would go negative and
just set it to zero.
Fixes:
1a9bf8146 ("Add option to ignore thinktime for rated IO")
Fixes: https://github.com/axboe/fio/issues/1588
Link: https://lore.kernel.org/fio/1689354334-131024-1-git-send-email-mikelley@microsoft.com/T/#u
Signed-off-by: Michael Kelley <mikelley@microsoft.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Fri, 14 Jul 2023 16:58:34 +0000 (12:58 -0400)]
stat: add diskutil aggregated sectors to normal output
Since we are now collecting sectors in the disk utilization data we
should include them in the aggregated data as well.
I tested this with an LVM mirror. I also tested this on an mdadm mirror
but all the aggregated and slave data was zero.
Fixes:
75cbc26d500fc5f7e36f6203c9b8e08b9c6f007c ("diskutil: Report how
many sectors have been read and written")
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Fri, 14 Jul 2023 16:36:20 +0000 (12:36 -0400)]
stat: add new diskutil sectors to json output
A recent commit added sectors read/written to the disk utilization data.
Allow these counts to also appear in the JSON output.
Fixes:
75cbc26d500fc5f7e36f6203c9b8e08b9c6f007c ("diskutil: Report how
many sectors have been read and written")
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Jens Axboe [Thu, 13 Jul 2023 21:28:20 +0000 (15:28 -0600)]
Merge branch 'master' of https://github.com/bvanassche/fio
* 'master' of https://github.com/bvanassche/fio:
diskutil: Report how many sectors have been read and written
diskutil: Fix a debug statement in get_io_ticks()
diskutil: Simplify get_io_ticks()
diskutil: Remove casts from get_io_ticks()
diskutil: Improve disk utilization data structure documentation
Bart Van Assche [Thu, 13 Jul 2023 19:44:54 +0000 (12:44 -0700)]
diskutil: Report how many sectors have been read and written
It is useful to know how much data has been read and/or written. Report
this information.
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Bart Van Assche [Thu, 13 Jul 2023 17:04:06 +0000 (10:04 -0700)]
diskutil: Fix a debug statement in get_io_ticks()
Report correctly whether or not reading statistics succeeded.
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Bart Van Assche [Thu, 13 Jul 2023 17:03:08 +0000 (10:03 -0700)]
diskutil: Simplify get_io_ticks()
Remove the sectors[] array. Remove the set-but-not-used in_flight variable.
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Bart Van Assche [Thu, 13 Jul 2023 16:54:30 +0000 (09:54 -0700)]
diskutil: Remove casts from get_io_ticks()
This patch does not change the behavior of the code.
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Bart Van Assche [Thu, 13 Jul 2023 16:54:22 +0000 (09:54 -0700)]
diskutil: Improve disk utilization data structure documentation
Document the meaning of the members of struct disk_util_stats.
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Vincent Fu [Thu, 13 Jul 2023 16:07:19 +0000 (12:07 -0400)]
options: add code for FDP pli selection use in client/server mode
For every new option, we need to convert it from the host's storage
format to the on-wire protocol and back in order to be able to use it in
client/server mode.
Fixes:
d3e310c531059fb606f04819c362b4d46c518b84 ("fdp: support random placement id selection")
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Ankit Kumar [Wed, 12 Jul 2023 10:20:41 +0000 (15:50 +0530)]
engines/xnvme: add support for fdp
Add FDP support to xnvme I/O engine. This support can be used only with
nvme-ns generic character device (/dev/ngXnY). The available backends are
--xnvme_async=io_uring_cmd and --xnvme_sync=nvme.
Add a xnvme-fdp config example file.
Update the minimum required xnvme version to 0.7.0
Signed-off-by: Ankit Kumar <ankit.kumar@samsung.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Ankit Kumar [Wed, 12 Jul 2023 10:20:40 +0000 (15:50 +0530)]
fdp: support random placement id selection
Allow user to either roundrobin or select random placement ID from
the available placement IDs.
Signed-off-by: Ankit Kumar <ankit.kumar@samsung.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Ankit Kumar [Wed, 12 Jul 2023 10:20:39 +0000 (15:50 +0530)]
fdp: fix placement id check
Number of reclaim unit handle descriptors are 1 based, whereas the
input placement id index / indices are 0 based. Add the correct check
for that.
Fixes:
a7e8aae0 ("fio: add fdp support ..")
Signed-off-by: Ankit Kumar <ankit.kumar@samsung.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Ankit Kumar [Wed, 12 Jul 2023 10:20:38 +0000 (15:50 +0530)]
fdp: use macros
use macros for directive type and max ruhs.
Signed-off-by: Ankit Kumar <ankit.kumar@samsung.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Jueji Yang [Thu, 6 Jul 2023 12:07:28 +0000 (20:07 +0800)]
fix: io_uring sqpoll issue_time empty when kernel not yet read sq
In io_uring sqpoll mode, when kernel side thread has not yet read
the sqring before second fio_ioring_commit() called, the
sq_ring.head will remain the same. The second
fio_ioring_commit() will initialize the wrong io_u's issue_time.
The old(in head) io_u‘s issue_time will to be initialized twice and
new(in tail - 1) io_u's issue_time will not to be initialized.
This problem will cause clat is weird, sometimes larger than lat.
Signed-off-by: Jueji Yang <jueji.yang@gmail.com>
Bart Van Assche [Wed, 5 Jul 2023 21:29:15 +0000 (14:29 -0700)]
zbd: Support finishing zones on Android
BLKFINISHZONE is missing from older versions of the Android NDK header
files. Hence, define BLKFINISHZONE if it has not been defined and detect
at runtime whether or not the kernel supports finishing zones.
Cc: Damien Le Moal <dlemoal@kernel.org>
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Link: https://lore.kernel.org/r/20230705212915.3373438-1-bvanassche@acm.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Vincent Fu [Tue, 27 Jun 2023 20:17:10 +0000 (20:17 +0000)]
t/nvmept: add trim test with ioengine options enabled
Add a test for a trim workload with ioengine options enabled like the
ones we have for read and write. fixedbufs cannot be enabled for a
trim-only workload because fio does not allocate data buffers for these
workloads.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Tue, 27 Jun 2023 20:16:13 +0000 (20:16 +0000)]
t/nvmept: add check for iodepth
Make sure that we achieve the iodepth specified in the job options.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Tue, 27 Jun 2023 19:19:11 +0000 (19:19 +0000)]
engines/io_uring: remove dead code related to trim
Now that we are no longer using an NVMe IOCTL to send io_uring_cmd trim
commands we can just use the existing pathway to carry out synchronous
trim commands for zoned devices. So we no longer need this code.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Tue, 27 Jun 2023 18:48:53 +0000 (18:48 +0000)]
engines/io_uring_cmd: make trims async
Instead of using a synchronous IOCTL to send a trim/deallocate request, just
use the io_uring pass-through interface to send the dataset management
command with the deallocate request just like we already do for read and
write commands.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Jens Axboe [Wed, 5 Jul 2023 14:55:30 +0000 (08:55 -0600)]
Merge branch 'makefile-hardening-cpp-flags' of https://github.com/proact-de/fio
* 'makefile-hardening-cpp-flags' of https://github.com/proact-de/fio:
Keep C pre processor hardening build flags.
Martin Steigerwald [Tue, 4 Jul 2023 12:29:14 +0000 (14:29 +0200)]
Keep C pre processor hardening build flags.
This allows for distributions like Debian to apply hardening flags
without patching the makefile.
Signed-off-by: Martin Steigerwald <martin.steigerwald@proact.de>
Jens Axboe [Mon, 3 Jul 2023 15:16:45 +0000 (09:16 -0600)]
fio/server: fix confusing sk_out check
The previous assert check we had here just checked for sk_out->sk being
-1, but if sk_out itself was set.
Fixes:
83276370ce4d ("fixed compiler warnings if NDEBUG enabled in core code")
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Jens Axboe [Mon, 3 Jul 2023 14:20:01 +0000 (08:20 -0600)]
Merge branch 'improvement/fix-warnings-if-NDEBUG-enabled' of https://github.com/dpronin/fio
* 'improvement/fix-warnings-if-NDEBUG-enabled' of https://github.com/dpronin/fio:
fixed compiler warnings if NDEBUG enabled in test code
fixed compiler warnings if NDEBUG enabled in core code
Jens Axboe [Mon, 3 Jul 2023 14:19:07 +0000 (08:19 -0600)]
Merge branch 'libaio/actual_min_algo_update' of https://github.com/dpronin/fio
* 'libaio/actual_min_algo_update' of https://github.com/dpronin/fio:
use 'min' macro to find out next value of actual_min in libaio
Vincent Fu [Tue, 20 Jun 2023 18:11:36 +0000 (14:11 -0400)]
init: don't adjust time units again for subjobs
We adjust max_latency and latency_target values to be nsec internally.
Make sure we do this only once for the parent job and don't do it a
second time for a subjob.
Fixes: https://github.com/axboe/fio/issues/1582
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Fri, 16 Jun 2023 14:41:25 +0000 (10:41 -0400)]
docs: clarify opendir description
Make explicit how opendir deals with colons in the path.
Fixes: https://github.com/axboe/fio/issues/1573
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Fri, 9 Jun 2023 23:59:14 +0000 (08:59 +0900)]
zbd: avoid Coverity defect report
Coverity reported a defect related to the local variable "in_flight":
Using an unreliable value of "in_flight" inside the second locked
section. If the data that "in_flight" depends on was changed by
another thread, this use might be incorrect.
The variable "in_flight" is thread local and other threads can not
change its value. Then the report should be false-positive. Just to
suppress the report, change reference timing of the valuable.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Link: https://lore.kernel.org/r/20230609235914.1376567-1-shinichiro.kawasaki@wdc.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Shin'ichiro Kawasaki [Thu, 8 Jun 2023 07:06:08 +0000 (16:06 +0900)]
t/zbd: test write zone accounting of trim workload
Recent commit fixed the bug of the write zone accounting of trim
workload. Add a test case which confirms the fix.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Thu, 8 Jun 2023 07:06:07 +0000 (16:06 +0900)]
t/zbd: test write zone accounting of almost full zones
Recent commit fixed the bug of the write zone accounting for almost full
zones. Add a test case which confirms the fix.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Thu, 8 Jun 2023 07:06:06 +0000 (16:06 +0900)]
t/zbd: reset zones before tests with max_open_zones option
After the recent fix, fio no longer resets zones when it finds more
zones in open condition than the max_open_zones option. This results in
failure of test cases 12, 13, 29, 32, 48 and 51. To avoid the failures,
reset zones at the beginning of the test cases.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Thu, 8 Jun 2023 07:06:05 +0000 (16:06 +0900)]
zbd: fix write zone accounting of trim workload
The commit
e3be810bf0fd ("zbd: Support zone reset by trim") supported
trim for zonemode=zbd by introducing the function zbd_do_io_u_trim(),
which calls zbd_reset_zone(). However, it did not call
zbd_write_zone_put() to the trim target zone, then trim operation
resulted in wrong accounting of write zones.
To fix the issue, call zbd_write_zone_put() from zbd_reset_zone(). To
cover the case to reset zones without a zbd_write_zone_put() call,
prepare another function __zbd_reset_zone(). While at it, simplify
zbd_reset_zones() by calling the modified zbd_reset_zone().
Of note is that the constifier of the argument td of do_io_u_trim() is
removed since zbd_write_zone_put() requires changes in that argument.
Fixes:
e3be810bf0fd ("zbd: Support zone reset by trim")
Suggested-by: Niklas Cassel <niklas.cassel@wdc.com>
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Thu, 8 Jun 2023 07:06:04 +0000 (16:06 +0900)]
zbd: fix write zone accounting of almost full zones
For zonemode=zbd, fio checks condition of each zone and account it as
write target zone if it has open condition. However, when such a zone in
open condition is almost full and its remainder area for write is
smaller than the block size, fio does not handle it as a write target
zone. This causes difference between open zones accounting on the device
and write target zones accounting by fio. It results in unexpected
max_open_zones limit failure.
Avoid the zone accounting difference by handling the almost full zones
as write target zones at fio start. Introduce the helper function
__zbd_write_zone_get() which does same operation as zbd_write_zone_get()
except the check for the almost full zones. At fio start, call
__zbd_write_zone_get() so that almost full zones are added to write
target zones. During fio workload run, call zbd_write_zone_get() so that
the almost full zones are not chosen for write target.
Suggested-by: Niklas Cassel <niklas.cassel@wdc.com>
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Thu, 8 Jun 2023 07:06:03 +0000 (16:06 +0900)]
zbd: do not reset extra zones in open conditions
The commit
954217b90191 ("zbd: Initialize open zones list referring zone
status at fio start") introduced zone resets for zones in open condition
which exceeds the limit of max_open_zones. However, this zone reset may
break data in the zones even when fio does no write to them. Avoid the
zone reset and report it as an error.
Fixes:
954217b90191 ("zbd: Initialize open zones list referring zone status at fio start")
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Shin'ichiro Kawasaki [Thu, 8 Jun 2023 07:06:02 +0000 (16:06 +0900)]
zbd: rename 'open zones' to 'write zones'
Current fio code for zonemode=zbd uses the word 'open zone' to mean the
zones that fio jobs write to. Before fio starts writing to a zone, it
calls zbd_open_zone(). When fio completes writing to a zone, it calls
zbd_close_zone(). This wording is good for zoned block devices with
max_open_zones limit, such as ZBC and ZAC devices. The devices use same
word 'open' to express the zone condition that the devices assign
resources for data write to zones. However, the word 'open' gets
confusing to support zoned block devices which has max_active_zones
limit, such as ZNS devices. These devices have both 'open' and 'active'
keywords to mean two different kinds of resources on the device. This
'active' status does not fit with the 'open zone' wording in the fio
code. Also, the word 'open' zone in fio code does not always match with
the 'open' condition of zones on the device (e.g. when
--ignore_zone_limits option is specified).
To avoid the confusion, stop using the word 'open zone' in the fio code.
Instead, use the word 'write zone' to mean that the zone is the write
target. When fio starts a write to a zone, it adds the zone to
write_zones array. When fio completes writing to a zone, it removes the
zone from the write_zones array. For this purpose, rename struct fields,
functions and a macro:
ZBD_MAX_OPEN_ZONES -> ZBD_MAX_WRITE_ZONES
struct fio_zone_info
open -> write
struct thread_data
num_open_zones -> num_write_zones
struct zoned_block_device_info:
max_open_zones -> max_write_zones
num_open_zones -> num_write_zones
open_zones[] -> write_zones[]
zbd_open_zone() -> zbd_write_zone_get()
zbd_close_zone() -> zbd_write_zone_put()
zbd_convert_to_open_zone() -> zbd_convert_to_write_zone()
To match up these changes, rename local variables and goto labels. Also
rephrase code comments.
Of note is that this rename is only for the fio code. The fio options
max_open_zones and job_max_open_zones are not renamed to not confuse
users.
Suggested-by: Niklas Cassel <niklas.cassel@wdc.com>
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 7 Jun 2023 22:45:49 +0000 (22:45 +0000)]
t/strided: increase minumum recommended size to 64MiB
Test 8 has offset=32M. So it fails with a 32MiB file. Increase the
minimum recommended test file/device size to 64MiB.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 7 Jun 2023 21:24:40 +0000 (21:24 +0000)]
t/strided: adapt to use fiotestlib
Use the FioJobCmdTest class and the run_fio_test runner to execute the
tests.
Also update run-fio-tests.py to accommodate the new way of specifying
the path to the fio executable.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 7 Jun 2023 21:21:50 +0000 (21:21 +0000)]
t/fiotestlib: add ability to ingest iops logs
Enhance the FioJobCmdTest class with the ability to read in an IOPS log
if one was generated during the course of the test run.
This reads in only the first IOPS log written as a result of
--write_iops_log.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 7 Jun 2023 16:49:18 +0000 (16:49 +0000)]
t/nvmept: adapt to use fiotestlib
Use the FioJobCmdTest class and the test runner from fiotestlib.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 7 Jun 2023 15:21:31 +0000 (15:21 +0000)]
t/readonly: adapt to use fiotestlib
Use the test runner and testclass provided in fiotestlib.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 7 Jun 2023 00:00:23 +0000 (20:00 -0400)]
t/random_seed: fixes from pylint
- Use % formatting for logging.debug
- Eliminate f-string without interpolated values
- Iterate with items() instead of just over keys
- Remove unused subprocess import
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 7 Jun 2023 13:49:18 +0000 (13:49 +0000)]
t/random_seed: use methods provided in fiotestlib to run tests
Adapt random_seed.py to use the new FioJobCmdTest class. Also use the
test runner from fiotestlib. This reduces code duplication.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Tue, 6 Jun 2023 22:13:15 +0000 (22:13 +0000)]
t/random_seed: use logging module for debug prints
Instead of having 'if self.debug:' lines all over the place, use the
logging module for debug messages.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 7 Jun 2023 13:47:53 +0000 (13:47 +0000)]
t/fiotestlib: add class for command-line fio job
Add a separate class for running a fio job with all of the options
provided on the command line (instead of in a job file).
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 7 Jun 2023 00:18:34 +0000 (20:18 -0400)]
t/fiotestlib: record test command in more useful format
Instead of recording the test command as a Python object, record it as a
string with spaces delimiting each of the paramters. This way we can use
it to directly issue the command in a shell.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Tue, 6 Jun 2023 20:38:21 +0000 (20:38 +0000)]
t/fiotestlib: rearrange constructor and setup steps
Make the constructor and setup steps more sensible. The constructor now
sets variables that should be fixed throughout the execution of the
test. Some of the setup steps may depend on values set by the
constructor. So keeps those separate.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Mon, 5 Jun 2023 18:06:17 +0000 (18:06 +0000)]
t/fiotestlib: use f-string for formatting
Take advantage of running on modern Python versions and use an f-string
for formatting.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Mon, 5 Jun 2023 17:59:55 +0000 (17:59 +0000)]
t/fiotestlib: use 'with' for opening files
Use with when opening files to relieve us of the need to explicitly
close the files.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Mon, 5 Jun 2023 17:46:19 +0000 (17:46 +0000)]
t/fiotestlib: use dictionaries for filenames and paths
Instead of separate variables for all the different filenames and paths,
use dictionaries for the filenames and paths.
This involves changing the function signature for the constructor and
setup() functions so that parameters are passed to setup() instead of
the constructor. This is because the base class defines the filenames
dictionary but FioJobFileTest needs to put an entry into the dictionary
before calling the base class constructor.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Fri, 2 Jun 2023 19:04:31 +0000 (19:04 +0000)]
t/run-fio-tests: move get_file outside of FioJobFileTest
There's no reason for this helper function to be part of a class. Just
make it an independent helper.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Fri, 2 Jun 2023 18:55:08 +0000 (18:55 +0000)]
t/run-fio-tests: rename FioJobTest to FioJobFileTest
We have two different types of tests based on fio jobs. The ones
referred to by FioJobFileTest consist of running a fio job file. It's
also possible to run a fio job test with options specified on the
command line. Such a class will be defined later.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Fri, 2 Jun 2023 16:25:50 +0000 (16:25 +0000)]
t/run-fio-tests: split source file
This is the first step in creating a test library that can be used by
other python test scripts to reduce code duplication.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Thu, 1 Jun 2023 14:20:17 +0000 (14:20 +0000)]
t/run-fio-tests: address issues identified by pylint
- use f strings
- use Python3 syntax for parent classes
- other small cleanups
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 31 May 2023 19:55:55 +0000 (19:55 +0000)]
t/run-fio-tests: integrate t/nvmept.py
Running t/nvmept.py requires that the test runner provide an NVMe
character device test target. t/nvmept.py will be skipped unless an NVMe
character device test target is provided.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Fri, 26 May 2023 23:05:12 +0000 (23:05 +0000)]
t/nvmept.py: test script for io_uring_cmd NVMe pass through
Test basic functionality of the io_uring_cmd ioengine with NVMe
pass-through commands.
This script starts with basic sequential and random read, write, trim,
readwrite, and trimwrite workloads. It also runs sequential and random
write workloads with verification. Finally it runs random read and write
workloads with almost all of the ioengine options enabled. The only
ioengine option not exercised is hipri because the NVMe driver must be
loaded with poll_queues set for this to work.
Since this is a destructive test the target device must be specified on
the command line.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Sat, 27 May 2023 00:09:53 +0000 (20:09 -0400)]
ci: disable tls for msys2 builds
The same tls issue that occurred with AppVeyor msys2 builds has appeared
in GitHub Actions msys2 builds. Disable thread local storage for GitHub
Actions msys2 builds as well.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Tue, 25 Apr 2023 18:22:26 +0000 (18:22 +0000)]
ci: upload tagged GitHub Actions Windows installers as releases
Since we are no long using AppVeyor for Windows tests, we can use the
installers built by GitHub Actions for Windows releases.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Vincent Fu [Wed, 24 May 2023 13:40:55 +0000 (09:40 -0400)]
ci: stop using AppVeyor for Windows builds
Stop running Windows tests using AppVeyor since it only runs tests
serially. GitHub Actions Windows tests have been running for a few weeks
and seem to be working ok.
Signed-off-by: Vincent Fu <vincent.fu@samsung.com>
Jens Axboe [Tue, 23 May 2023 18:33:03 +0000 (12:33 -0600)]
Fio 3.35
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Vincent Fu [Tue, 23 May 2023 12:42:56 +0000 (08:42 -0400)]
Merge branch 'master' of https://github.com/bvanassche/fio
* 'master' of https://github.com/bvanassche/fio:
zbd: Report the zone capacity
zbd: Make an error message more detailed