Age | Commit message (Collapse) | Author |
|
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
eta.c
fio.h
init.c
options.c
stat.c
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
With network testing, it's often desirable to measure in terms of
kilobits/megabits rather than kilobytes/megabytes. This adds an option named
'unit_base' which can be set to either '1' or '8', where '1' means represent in
terms of bits and '8' means to represent rate in terms of bytes.
Signed-off-by: Steven Noonan <steven@uplinklabs.net>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
This allows for representing I/O rates in terms of e.g. megabits (Mb) versus
megabytes (MB).
Signed-off-by: Steven Noonan <steven@uplinklabs.net>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
init.c
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
For certain situations, it's handy to force a new line in
the ETA output. It allows you to easily track what
happened, without having to do detailed logging.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
Makefile
configure
fio.h
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
If zonesize was bigger than zoneskip, we could encounter a divide by
zero when calculating the number of bytes.
Additionally, the math was just wrong for most cases of zone settings.
Improve that.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
Makefile
fio.h
parse.c
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
If they are being redirected to a file with --output, then
we can still use the normal runtime ETA output on stdout.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
Makefile
client.c
configure
fio.c
fio.h
server.c
server.h
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
If this is set, then fio will sum and display just a single set
of statistics for any IO type. By default, fio accounts and reports
each data direction separately.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
Makefile
backend.c
client.c
fio.c
fio.h
ioengine.h
options.c
os/os-linux.h
server.c
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
We assume 50/50 for mixed workloads. That's silly, use the actual
number specified instead.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
Makefile
backend.c
client.c
fio.h
options.c
parse.c
parse.h
server.c
server.h
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
Makefile
backend.c
client.c
fio.h
init.c
io_ddir.h
options.c
server.h
stat.c
stat.h
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Right now we have normal, terse, and json output. Lets add a parameter
that controls how to output results, instead of having options for
both terse and json outputs. If we are going to add a 4th output
type in the future, it's only going to get more messy.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
We sum up the three data direction primitives a lot, this is
more readable.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
This only works on Linux so far, and it's always sync given what
the interface to the kernel looks like. Also restricted to pure
block devices.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
eta.c
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Currently we sum up read and write IOPS/BW rates, but that reads
a bit strange when a given workload only does reads OR writes.
The user then thinks that fio mis-parsed the setting, reading
twice as much as expected.
Only sum up for the read OR write side if one direction is given.
For a mixed workload, it's still the sum of both.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
client.c
eta.c
server.c
server.h
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Same fix as 033bbb51 essentially. Since mtime is a 1000th of a second,
for the usual option of having 1024 be the KB base, we end up being
off by 1.024 if we don't multiply by 1000 before dividing by the
runtime (and then dividing by 1024 to get to next power-of-2).
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Conflicts:
Makefile
backend.c
client.c
fio.h
os/windows/install.wxs
server.c
server.h
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
We simply overwrite our status output buffer, not a terribly
good idea.
Reported-by: Roger Sibert <Roger_Sibert@xyratex.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
|
|
We have 'X' for exited with error, add 'K' for killed by
signal as well.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Instead of just printing a '_' for a job that has exited,
allow the user to tell if the job exited with an error or
not. A normally reaped job that ran to completion without
errors will have the '_' displayed. If the job exited with
an error, then an 'X' will be displayed instead.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
The whole layout will probably be changed, but for now it
demonstrates how to properly integrate with the net client
to handle the data and output it.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Signed-off-by: Stephen M. Cameron <stephenmcameron@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
The thread status display uses printf to stdout.
Need a way to capture it for the gui.
Signed-off-by: Stephen M. Cameron <stephenmcameron@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Also changes the 'serial' of the command to a tag, that's passed
back and forth for commands that need to use it.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
No more text passing for ETA.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|
|
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
|
|
And shrink OSX max default number of jobs supported. OSX has,
by default, a very small shared memory segment available.
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
|
|
Reported-by: Bruce Cran <bruce@cran.org.uk>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
|
|
There are a couple of problems with the relatively new ramp_in feature
of fio. First, the estimated time to completion did not correctly take
it into account and bounces around. Second and more importantly, the
runtime was including ramp in time in throughput calculations even
though the IO done during that time was ignored, thus making throughput
metrics incorrect. This patch fixes both.
Signed-off-by Steven Pratt <slpratt@austin.ibm.com>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
|
|
We do allocations, open files, printf, etc from the SIGALRM signal
handler which gets run every 250 msecs. This isn't necessarily
safe and could deadlock. Move it to thread context instead.
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
|
|
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|
|
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|
|
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|
|
Confuses more than it does good, drop it and default to just using KB,
MB, etc.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|
|
So now you can say 'limit writes to 10MB/sec' and have reads go
full throttle, for instance.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|
|
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
|