All of lore.kernel.org
 help / color / mirror / Atom feed
* Unable to replay blktrace with mixed workload
@ 2015-04-23 19:55 Brandon Schwartz
  2015-04-24 15:04 ` Jens Axboe
  0 siblings, 1 reply; 3+ messages in thread
From: Brandon Schwartz @ 2015-04-23 19:55 UTC (permalink / raw)
  To: fio

Using FIO 2.2.7, I'm trying to replay the following workload
(capturing it with blktrace and replaying with FIO on the same device)

 sudo fio --name=rwmix --filename=/dev/sdd --blocksize=128k
--readwrite=randrw --rwmixread=75 --rwmixwrite=25 --runtime=60

And I get the following error:

fio: pid=21428, err=12/file:memory.c:242, func=iomem allocation,
error=Cannot allocate memory

Older versions of FIO (2.1.*) seem to be able to replay the blktrace
without that error, but those versions of FIO don't always seem to
respect the timing of IOs (if there is idle time for example).

Any idea what could be causing the problem?

Regards,
Brandon

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

* Re: Unable to replay blktrace with mixed workload
  2015-04-23 19:55 Unable to replay blktrace with mixed workload Brandon Schwartz
@ 2015-04-24 15:04 ` Jens Axboe
  2015-04-24 18:14   ` Brandon Schwartz
  0 siblings, 1 reply; 3+ messages in thread
From: Jens Axboe @ 2015-04-24 15:04 UTC (permalink / raw)
  To: Brandon Schwartz, fio

On 04/23/2015 01:55 PM, Brandon Schwartz wrote:
> Using FIO 2.2.7, I'm trying to replay the following workload
> (capturing it with blktrace and replaying with FIO on the same device)
>
>   sudo fio --name=rwmix --filename=/dev/sdd --blocksize=128k
> --readwrite=randrw --rwmixread=75 --rwmixwrite=25 --runtime=60
>
> And I get the following error:
>
> fio: pid=21428, err=12/file:memory.c:242, func=iomem allocation,
> error=Cannot allocate memory
>
> Older versions of FIO (2.1.*) seem to be able to replay the blktrace
> without that error, but those versions of FIO don't always seem to
> respect the timing of IOs (if there is idle time for example).
>
> Any idea what could be causing the problem?

There were a few bugs in there. Can you try current -git? Just committed 
a change that should improve things for you.

-- 
Jens Axboe



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

* Re: Unable to replay blktrace with mixed workload
  2015-04-24 15:04 ` Jens Axboe
@ 2015-04-24 18:14   ` Brandon Schwartz
  0 siblings, 0 replies; 3+ messages in thread
From: Brandon Schwartz @ 2015-04-24 18:14 UTC (permalink / raw)
  To: Jens Axboe; +Cc: fio

Thanks, but now it seems to convert the blktrace replay into all reads
and increase the run time to 20minutes (from 60seconds).

fio-2.2.7-24-g7c30 is the latest right?



On Fri, Apr 24, 2015 at 9:04 AM, Jens Axboe <axboe@kernel.dk> wrote:
> On 04/23/2015 01:55 PM, Brandon Schwartz wrote:
>>
>> Using FIO 2.2.7, I'm trying to replay the following workload
>> (capturing it with blktrace and replaying with FIO on the same device)
>>
>>   sudo fio --name=rwmix --filename=/dev/sdd --blocksize=128k
>> --readwrite=randrw --rwmixread=75 --rwmixwrite=25 --runtime=60
>>
>> And I get the following error:
>>
>> fio: pid=21428, err=12/file:memory.c:242, func=iomem allocation,
>> error=Cannot allocate memory
>>
>> Older versions of FIO (2.1.*) seem to be able to replay the blktrace
>> without that error, but those versions of FIO don't always seem to
>> respect the timing of IOs (if there is idle time for example).
>>
>> Any idea what could be causing the problem?
>
>
> There were a few bugs in there. Can you try current -git? Just committed a
> change that should improve things for you.
>
> --
> Jens Axboe
>


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

end of thread, other threads:[~2015-04-24 18:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-23 19:55 Unable to replay blktrace with mixed workload Brandon Schwartz
2015-04-24 15:04 ` Jens Axboe
2015-04-24 18:14   ` Brandon Schwartz

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.