From: Benjamin LaHaise <bcrl@redhat.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-aio@kvack.org
Subject: Re: [RFC] [PATCH] 2.5.35 patch for making DIO async
Date: Wed, 18 Sep 2002 12:04:47 -0400 [thread overview]
Message-ID: <20020918120447.F6398@redhat.com> (raw)
In-Reply-To: <200209181558.g8IFwNp14249@eng2.beaverton.ibm.com>; from pbadari@us.ibm.com on Wed, Sep 18, 2002 at 08:58:22AM -0700
On Wed, Sep 18, 2002 at 08:58:22AM -0700, Badari Pulavarty wrote:
> Thanks for looking at the patch. Patch needed few cleanups to get it
> working. Here is the status so far..
>
> 1) I tested synchronous raw read/write. They perform almost same as
> without this patch. I am looking at why I can't match the performance.
> (I get 380MB/sec on 40 dd's on 40 disks without this patch.
> I get 350MB/sec with this patch).
Hmm, we should try to improve that. Have you tried profiling a long run?
> 2) wait_on_sync_kiocb() needed blk_run_queues() to make regular read/
> write perform well.
That should be somewhat conditional, but for now it sounds like the right
thing to do.
> 3) I am testing aio read/writes. I am using libaio.0.3.92.
> When I try aio_read/aio_write on raw device, I am get OOPS.
> Can I use libaio.0.3.92 on 2.5 ? Are there any interface
> changes I need to worry between 2.4 and 2.5 ?
libaio 0.3.92 should work on 2.5. Could you send me a copy of the
decoded Oops?
-ben
--
GMS rules.
next prev parent reply other threads:[~2002-09-18 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 21:03 [RFC] [PATCH] 2.5.35 patch for making DIO async Badari Pulavarty
2002-09-18 11:51 ` Benjamin LaHaise
2002-09-18 15:58 ` Badari Pulavarty
2002-09-18 16:04 ` Benjamin LaHaise [this message]
2002-09-18 16:30 ` Badari Pulavarty
2002-09-18 20:47 ` Badari Pulavarty
2002-09-19 10:52 ` Suparna Bhattacharya
2002-09-19 11:36 ` Suparna Bhattacharya
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=20020918120447.F6398@redhat.com \
--to=bcrl@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.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.