* --latency-log
@ 2010-06-23 4:40 YAMAMOTO Takashi
2010-06-23 12:49 ` --latency-log Jens Axboe
0 siblings, 1 reply; 2+ messages in thread
From: YAMAMOTO Takashi @ 2010-06-23 4:40 UTC (permalink / raw)
To: fio
hi,
the --latency-log option merely sets the write_lat_log global variable,
which doesn't seem to be used at all.
YAMAMOTO Takashi
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: --latency-log
2010-06-23 4:40 --latency-log YAMAMOTO Takashi
@ 2010-06-23 12:49 ` Jens Axboe
0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2010-06-23 12:49 UTC (permalink / raw)
To: YAMAMOTO Takashi; +Cc: fio
On 2010-06-23 06:40, YAMAMOTO Takashi wrote:
> hi,
>
> the --latency-log option merely sets the write_lat_log global variable,
> which doesn't seem to be used at all.
So question is how to handle that... The equivalent bw option logs
aggregate bandwidth. Either we drop it, or we make td->o.write_lat_log
inherit this setting.
--
Jens Axboe
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-06-23 12:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-23 4:40 --latency-log YAMAMOTO Takashi
2010-06-23 12:49 ` --latency-log Jens Axboe
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox