Re: io_u->flags & IO_U_F_FLIGHT failed errors when using libaio

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/06/2015 04:32 PM, Of wrote:
Yes Jens it is ppc64

I'm pretty sure we have some memory ordering issues, or perhaps the barriers on ppc64 are just wrong. I'll have to check them.

The job:

cmd="$FIO --name=test  --group_reporting=1 --ioengine=libaio
--invalidate=1 --iodepth=32 --bs=4K --filename=/dev/sde --rw=randread
--direct=1 --buffered=0 --time_based --runtime=300 --numjobs=64"

does indeed have 32 * 64 potentially pending, which is huge. So there are valid questions on whether this is really what you want. But regardless of that, it should not pose a problem for fio.

Is this on Linux? If so, can you send the output of /proc/cpuinfo, so I can see what CPU this is exactly.

--
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Linux SCSI]     [Linux IDE]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux