X-Git-Url: https://git.kernel.dk/?p=fio.git;a=blobdiff_plain;f=fio.1;h=804ee47c943626761760113ef932dc1ce625d065;hp=3224e9a1d88ae7a7088e980b2dcd2c5472cbbcee;hb=c32ba107891e7dcd7ced0de16b0f85f432b5d0a5;hpb=725927803e15a56fafc4952a78c6810efae6cebb diff --git a/fio.1 b/fio.1 index 3224e9a1..804ee47c 100644 --- a/fio.1 +++ b/fio.1 @@ -1033,6 +1033,8 @@ Normal (Gaussian) distribution .TP .B zoned Zoned random distribution +.B zoned_abs +Zoned absolute random distribution .RE .P When using a \fBzipf\fR or \fBpareto\fR distribution, an input value is also @@ -1068,7 +1070,27 @@ example, the user would do: random_distribution=zoned:60/10:30/20:8/30:2/40 .RE .P -similarly to how \fBbssplit\fR works for setting ranges and percentages +A \fBzoned_abs\fR distribution works exactly like the\fBzoned\fR, except that +it takes absolute sizes. For example, let's say you wanted to define access +according to the following criteria: +.RS +.P +.PD 0 +60% of accesses should be to the first 20G +.P +30% of accesses should be to the next 100G +.P +10% of accesses should be to the next 500G +.PD +.RE +.P +we can define an absolute zoning distribution with: +.RS +.P +random_distribution=zoned:60/10:30/20:8/30:2/40 +.RE +.P +Similarly to how \fBbssplit\fR works for setting ranges and percentages of block sizes. Like \fBbssplit\fR, it's possible to specify separate zones for reads, writes, and trims. If just one set is given, it'll apply to all of them. @@ -1525,7 +1547,8 @@ for more info on GUASI. .B rdma The RDMA I/O engine supports both RDMA memory semantics (RDMA_WRITE/RDMA_READ) and channel semantics (Send/Recv) for the -InfiniBand, RoCE and iWARP protocols. +InfiniBand, RoCE and iWARP protocols. This engine defines engine +specific options. .TP .B falloc I/O engine that does regular fallocate to simulate data transfer as @@ -1654,10 +1677,14 @@ The TCP or UDP port to bind to or connect to. If this is used with this will be the starting port number since fio will use a range of ports. .TP -.BI (netsplice,net)hostname \fR=\fPstr -The hostname or IP address to use for TCP or UDP based I/O. If the job is -a TCP listener or UDP reader, the hostname is not used and must be omitted -unless it is a valid UDP multicast address. +.BI (rdma)port +The port to use for RDMA-CM communication. This should be the same +value on the client and the server side. +.TP +.BI (netsplice,net, rdma)hostname \fR=\fPstr +The hostname or IP address to use for TCP, UDP or RDMA-CM based I/O. +If the job is a TCP listener or UDP reader, the hostname is not used +and must be omitted unless it is a valid UDP multicast address. .TP .BI (netsplice,net)interface \fR=\fPstr The IP address of the network interface used to send or receive UDP @@ -1757,6 +1784,21 @@ libhdfs will create chunk in this HDFS directory. .TP .BI (libhdfs)chunk_size The size of the chunk to use for each file. +.TP +.BI (rdma)verb \fR=\fPstr +The RDMA verb to use on this side of the RDMA ioengine +connection. Valid values are write, read, send and recv. These +correspond to the equivalent RDMA verbs (e.g. write = rdma_write +etc.). Note that this only needs to be specified on the client side of +the connection. See the examples folder. +.TP +.BI (rdma)bindname \fR=\fPstr +The name to use to bind the local RDMA-CM connection to a local RDMA +device. This could be a hostname or an IPv4 or IPv6 address. On the +server side this will be passed into the rdma_bind_addr() function and +on the client site it will be used in the rdma_resolve_add() +function. This can be useful when multiple paths exist between the +client and the server or in certain loopback configurations. .SS "I/O depth" .TP .BI iodepth \fR=\fPint @@ -2597,9 +2639,9 @@ completion latency below which 99.5% and 99.9% of the observed latencies fell, respectively. .TP .BI significant_figures \fR=\fPint -If using \fB\-\-output\-format\fR of `normal', set the significant figures -to this value. Higher values will yield more precise IOPS and throughput -units, while lower values will round. Requires a minimum value of 1 and a +If using \fB\-\-output\-format\fR of `normal', set the significant figures +to this value. Higher values will yield more precise IOPS and throughput +units, while lower values will round. Requires a minimum value of 1 and a maximum value of 10. Defaults to 4. .SS "Error handling" .TP