From: Chris Mason <chris.mason@oracle.com>
To: "Ananiev, Leonid I" <leonid.i.ananiev@intel.com>
Cc: Zach Brown <zach.brown@oracle.com>,
linux-aio@kvack.org, linux-kernel@vger.kernel.org,
Benjamin LaHaise <bcrl@kvack.org>,
Suparna bhattacharya <suparna@in.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] aio: propogate post-EIOCBQUEUED errors to completion event
Date: Tue, 20 Feb 2007 12:54:57 -0500 [thread overview]
Message-ID: <20070220175457.GS6133@think.oraclecorp.com> (raw)
In-Reply-To: <B41635854730A14CA71C92B36EC22AAC871D9D@mssmsx411>
On Tue, Feb 20, 2007 at 08:17:51PM +0300, Ananiev, Leonid I wrote:
> aio-stress command lines used for test
> 1) mem=1G in kernel boot param if you have more
> 2) mk2fs for test_file
> 3) dd if=/dev/zero of=<test_file> bs=1M count=1200
> 4) aiostress -s 1200m -o 2 -i 1 -r 16k <test_file>
>
Sorry, this aio-stress command line doesn't do O_DIRECT. Do you have
this bundled into a test script that I can try?
-chris
next prev parent reply other threads:[~2007-02-20 17:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 21:38 [PATCH 1/2] aio: create aio_ring_insert_entry() function Zach Brown
2007-02-19 21:38 ` [PATCH 2/2] aio: propogate post-EIOCBQUEUED errors to completion event Zach Brown
2007-02-19 22:48 ` Jeff Moyer
2007-02-19 22:57 ` Zach Brown
2007-02-20 16:57 ` Ananiev, Leonid I
2007-02-20 17:03 ` Chris Mason
2007-02-20 17:17 ` Ananiev, Leonid I
2007-02-20 17:54 ` Chris Mason [this message]
2007-02-20 21:09 ` Ananiev, Leonid I
2007-02-21 8:35 ` Ken Chen
2007-02-21 8:44 ` Ananiev, Leonid I
2007-02-21 18:24 ` Zach Brown
2007-02-21 19:15 ` Ananiev, Leonid I
2007-02-20 17:33 ` Ananiev, Leonid I
2007-02-20 18:26 ` Zach Brown
2007-02-21 14:13 ` Suparna Bhattacharya
2007-02-21 18:34 ` Zach Brown
2007-02-19 22:41 ` [PATCH 1/2] aio: create aio_ring_insert_entry() function Jeff Moyer
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=20070220175457.GS6133@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=leonid.i.ananiev@intel.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.com \
--cc=zach.brown@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 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.