From: charles zhuang <cjiazhuang@yahoo.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: fio@vger.kernel.org
Subject: Re: libaio ioengine cause initiator crash
Date: Mon, 8 Feb 2010 15:27:41 -0800 (PST) [thread overview]
Message-ID: <157216.71006.qm@web80807.mail.mud.yahoo.com> (raw)
In-Reply-To: <20100208221033.GW1025@kernel.dk>
>> If stgt is restricted to page size transfers, then it should set the
hardware block size to that (which would then cause fio with 2k bs and
O_DIRECT to error out, instead of crash).
Hi Jens,
Block size is not an issue. I can use other ioengine (like sync) to run thru the test with bs=2k & under, only libaio ioengine has this problem.
Besides, when I run fio with "--ioengine=sync" and "--iodepth=64", the initiator immediately crash. I know iodepth is only matter to aio type, but it shouldn't crash the kernel.
--
Jens Axboe
prev parent reply other threads:[~2010-02-08 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 21:57 libaio ioengine cause initiator crash charles zhuang
2010-02-08 22:10 ` Jens Axboe
2010-02-08 22:47 ` charles zhuang
2010-02-08 23:27 ` charles zhuang [this message]
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=157216.71006.qm@web80807.mail.mud.yahoo.com \
--to=cjiazhuang@yahoo.com \
--cc=fio@vger.kernel.org \
--cc=jens.axboe@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox