Make td_io_u_lock/unlock() explicit

[fio.git] / HOWTO

diff --git a/HOWTO b/HOWTO
index b7e18529749b16fc607db18fe7f250668eafe050..7bbd589838ed5dc3c4f9a6cb27e1e620c75a8e3d 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -1017,6 +1017,28 @@ Target file/device
        bandwidth and IOPS numbers fio only reads beyond the write pointer if
        explicitly told to do so. Default: false.
 
+.. option:: max_open_zones=int
+
+       When running a random write test across an entire drive many more
+       zones will be open than in a typical application workload. Hence this
+       command line option that allows to limit the number of open zones. The
+       number of open zones is defined as the number of zones to which write
+       commands are issued.
+
+.. option:: zone_reset_threshold=float
+
+       A number between zero and one that indicates the ratio of logical
+       blocks with data to the total number of logical blocks in the test
+       above which zones should be reset periodically.
+
+.. option:: zone_reset_frequency=float
+
+       A number between zero and one that indicates how often a zone reset
+       should be issued if the zone reset threshold has been exceeded. A zone
+       reset is submitted after each (1 / zone_reset_frequency) write
+       requests. This and the previous parameter can be used to simulate
+       garbage collection activity.
+
 
 I/O type
 ~~~~~~~~