From: Jens Axboe <axboe@kernel.dk>
To: Of <sendtold@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: io_u->flags & IO_U_F_FLIGHT failed errors when using libaio
Date: Sat, 07 Feb 2015 10:12:11 -0700 [thread overview]
Message-ID: <54D6476B.8070200@kernel.dk> (raw)
In-Reply-To: <94D849AD-CCC8-4DE5-842D-A5AA16F789CA@gmail.com>
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
next prev parent reply other threads:[~2015-02-07 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 20:03 io_u->flags & IO_U_F_FLIGHT failed errors when using libaio Lakshmi
2015-02-06 21:12 ` Andrey Kuzmin
2015-02-06 21:13 ` Jens Axboe
2015-02-06 23:32 ` Of
2015-02-07 17:12 ` Jens Axboe [this message]
2015-02-07 7:02 ` Sitsofe Wheeler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54D6476B.8070200@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sendtold@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.