diff options
author | Erwan Velu <erwan@enovance.com> | 2013-08-02 16:39:40 +0200 |
---|---|---|
committer | Erwan Velu <erwan@enovance.com> | 2013-08-05 17:10:00 +0200 |
commit | 9b7e600ddb531fd359322bbc14e358c10761fe57 (patch) | |
tree | ac584fe70751662f3b4d8d02490e8110bf40fb66 /io_u.c | |
parent | 8ff749cca16845a3172e22323489d20d8f99f9dd (diff) | |
download | fio-9b7e600ddb531fd359322bbc14e358c10761fe57.tar.gz |
iolog: Logging blocksize in IOPS traces
When saving bandwidth's with write_bw_log option, the last column
provides the blocksize used during the run.
When doing the same with write_io_log option, the last column was always
set to 0 which is confusing when reading the log file later.
This patch put both write_bw_log & write_io_log using the same semantic
by reporting the blocksize for every sample.
Diffstat (limited to 'io_u.c')
-rw-r--r-- | io_u.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1412,7 +1412,7 @@ static void account_io_completion(struct thread_data *td, struct io_u *io_u, if (!td->o.disable_bw) add_bw_sample(td, idx, bytes, &icd->time); - add_iops_sample(td, idx, &icd->time); + add_iops_sample(td, idx, bytes, &icd->time); } static long long usec_for_io(struct thread_data *td, enum fio_ddir ddir) |