From: Tomohiro Kusumi Date: Wed, 27 Jul 2016 13:37:12 +0000 (+0900) Subject: Mention cpuio never finishes without real I/O in documentation X-Git-Tag: fio-2.14~87 X-Git-Url: https://git.kernel.dk/?a=commitdiff_plain;h=3e93fc256cb4156518ec9720cda0a3d9c777c6f8;p=fio.git Mention cpuio never finishes without real I/O in documentation reap_threads() terminates cpuio threads only when there is at least one real I/O thread that is exiting. > if (*nr_running == cputhreads && !pending && realthreads) > fio_terminate_threads(TERMINATE_ALL); Signed-off-by: Tomohiro Kusumi Signed-off-by: Jens Axboe --- diff --git a/HOWTO b/HOWTO index ca1542d5..b9076d5e 100644 --- a/HOWTO +++ b/HOWTO @@ -757,7 +757,8 @@ ioengine=str Defines how the job issues io to the file. The following 85% of the CPU. In case of SMP machines, use numjobs= to get desired CPU usage, as the cpuload only loads a single - CPU at the desired rate. + CPU at the desired rate. A job never finishes + unless there is at least one non-cpuio job. guasi The GUASI IO engine is the Generic Userspace Asyncronous Syscall Interface approach diff --git a/fio.1 b/fio.1 index 0461d90e..a9abe3fc 100644 --- a/fio.1 +++ b/fio.1 @@ -656,7 +656,8 @@ and send/receive. This ioengine defines engine specific options. .TP .B cpuio Doesn't transfer any data, but burns CPU cycles according to \fBcpuload\fR and -\fBcpuchunks\fR parameters. +\fBcpuchunks\fR parameters. A job never finishes unless there is at least one +non-cpuio job. .TP .B guasi The GUASI I/O engine is the Generic Userspace Asynchronous Syscall Interface