Flexible I/O Tester development
 help / color / mirror / Atom feed
* no slat log
@ 2013-08-06 22:08 Dennis Jacobfeuerborn
  2013-08-07  9:10 ` Erwan Velu
  0 siblings, 1 reply; 5+ messages in thread
From: Dennis Jacobfeuerborn @ 2013-08-06 22:08 UTC (permalink / raw)
  To: fio@vger.kernel.org

Hi,
when I try to create logs with fio I get bw, iops, lat, clat and slat 
logs but the slat log always has a size of 0 bytes. Is this a bug or is 
data for this log only generated with specific options for fio?

Regards,
   Dennis

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: no slat log
  2013-08-06 22:08 no slat log Dennis Jacobfeuerborn
@ 2013-08-07  9:10 ` Erwan Velu
  2013-08-07 10:36   ` Dennis Jacobfeuerborn
  0 siblings, 1 reply; 5+ messages in thread
From: Erwan Velu @ 2013-08-07  9:10 UTC (permalink / raw)
  To: Dennis Jacobfeuerborn; +Cc: fio@vger.kernel.org

On 07/08/2013 00:08, Dennis Jacobfeuerborn wrote:
> Hi,
> when I try to create logs with fio I get bw, iops, lat, clat and slat 
> logs but the slat log always has a size of 0 bytes. Is this a bug or 
> is data for this log only generated with specific options for fio?
>
Dennis,

I've been trying this on my 2.1.2 with the following job :

[read-sda-4k-para]
bs=4k
filename=/dev/sda
rw=read
write_lat_log=lat.log

On my side, the slat file is perfectly filled.

Can you provide a testing procedure & the version you use ?

Cheers,


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: no slat log
  2013-08-07  9:10 ` Erwan Velu
@ 2013-08-07 10:36   ` Dennis Jacobfeuerborn
  2013-08-07 12:30     ` Erwan Velu
  2013-08-08 20:55     ` Jens Axboe
  0 siblings, 2 replies; 5+ messages in thread
From: Dennis Jacobfeuerborn @ 2013-08-07 10:36 UTC (permalink / raw)
  To: Erwan Velu; +Cc: fio@vger.kernel.org

On 07.08.2013 11:10, Erwan Velu wrote:
> On 07/08/2013 00:08, Dennis Jacobfeuerborn wrote:
>> Hi,
>> when I try to create logs with fio I get bw, iops, lat, clat and slat
>> logs but the slat log always has a size of 0 bytes. Is this a bug or
>> is data for this log only generated with specific options for fio?
>>
> Dennis,
>
> I've been trying this on my 2.1.2 with the following job :
>
> [read-sda-4k-para]
> bs=4k
> filename=/dev/sda
> rw=read
> write_lat_log=lat.log
>
> On my side, the slat file is perfectly filled.
>
> Can you provide a testing procedure & the version you use ?

I just tested the job above and these are the files produced:

[dennis@nexus fio]$ ls -l
total 11272
-rw-r--r--. 1 root   root   5767080  7. Aug 12:31 lat.log_clat.log
-rw-r--r--. 1 root   root   5767087  7. Aug 12:31 lat.log_lat.log
-rw-r--r--. 1 root   root         0  7. Aug 12:31 lat.log_slat.log
-rw-rw-r--. 1 dennis dennis      84  7. Aug 12:31 logtest.fio

There are not errors or warnings during the fio run so it's not clear 
why the file ends up being empty.

Regards,
   Dennis


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: no slat log
  2013-08-07 10:36   ` Dennis Jacobfeuerborn
@ 2013-08-07 12:30     ` Erwan Velu
  2013-08-08 20:55     ` Jens Axboe
  1 sibling, 0 replies; 5+ messages in thread
From: Erwan Velu @ 2013-08-07 12:30 UTC (permalink / raw)
  To: Dennis Jacobfeuerborn; +Cc: fio@vger.kernel.org

On 07/08/2013 12:36, Dennis Jacobfeuerborn wrote:
>
> I just tested the job above and these are the files produced:
>
> [dennis@nexus fio]$ ls -l
> total 11272
> -rw-r--r--. 1 root   root   5767080  7. Aug 12:31 lat.log_clat.log
> -rw-r--r--. 1 root   root   5767087  7. Aug 12:31 lat.log_lat.log
> -rw-r--r--. 1 root   root         0  7. Aug 12:31 lat.log_slat.log
> -rw-rw-r--. 1 dennis dennis      84  7. Aug 12:31 logtest.fio
>
> There are not errors or warnings during the fio run so it's not clear 
> why the file ends up being empty.

Are you running 2.1.2 ?
If so, can you provides the complete output of fio while running ?

Cheers,


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: no slat log
  2013-08-07 10:36   ` Dennis Jacobfeuerborn
  2013-08-07 12:30     ` Erwan Velu
@ 2013-08-08 20:55     ` Jens Axboe
  1 sibling, 0 replies; 5+ messages in thread
From: Jens Axboe @ 2013-08-08 20:55 UTC (permalink / raw)
  To: Dennis Jacobfeuerborn; +Cc: Erwan Velu, fio@vger.kernel.org

On 08/07/2013 04:36 AM, Dennis Jacobfeuerborn wrote:
> On 07.08.2013 11:10, Erwan Velu wrote:
>> On 07/08/2013 00:08, Dennis Jacobfeuerborn wrote:
>>> Hi,
>>> when I try to create logs with fio I get bw, iops, lat, clat and slat
>>> logs but the slat log always has a size of 0 bytes. Is this a bug or
>>> is data for this log only generated with specific options for fio?
>>>
>> Dennis,
>>
>> I've been trying this on my 2.1.2 with the following job :
>>
>> [read-sda-4k-para]
>> bs=4k
>> filename=/dev/sda
>> rw=read
>> write_lat_log=lat.log
>>
>> On my side, the slat file is perfectly filled.
>>
>> Can you provide a testing procedure & the version you use ?
> 
> I just tested the job above and these are the files produced:
> 
> [dennis@nexus fio]$ ls -l
> total 11272
> -rw-r--r--. 1 root   root   5767080  7. Aug 12:31 lat.log_clat.log
> -rw-r--r--. 1 root   root   5767087  7. Aug 12:31 lat.log_lat.log
> -rw-r--r--. 1 root   root         0  7. Aug 12:31 lat.log_slat.log
> -rw-rw-r--. 1 dennis dennis      84  7. Aug 12:31 logtest.fio
> 
> There are not errors or warnings during the fio run so it's not clear
> why the file ends up being empty.

slat only exists for async IO engines. For a sync workload, submission
and completion retrieval are not separate events, so you cannot do split
submission + completion stats.

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-08-08 20:56 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-06 22:08 no slat log Dennis Jacobfeuerborn
2013-08-07  9:10 ` Erwan Velu
2013-08-07 10:36   ` Dennis Jacobfeuerborn
2013-08-07 12:30     ` Erwan Velu
2013-08-08 20:55     ` Jens Axboe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox