From: Andrea Arcangeli <andrea@suse.de>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: performance of O_DIRECT on md/lvm
Date: Mon, 21 Jan 2002 15:41:25 +0100 [thread overview]
Message-ID: <20020121154125.A8292@athlon.random> (raw)
In-Reply-To: <200201181743.g0IHhO226012@street-vision.com.suse.lists.linux.kernel> <3C48607C.35D3DDFF@redhat.com.suse.lists.linux.kernel> <20020120201603.L21279@athlon.random.suse.lists.linux.kernel> <p734rlg90ga.fsf@oldwotan.suse.de> <20020121021224.O21279@athlon.random> <20020121003552.A12850@redhat.com>
In-Reply-To: <20020121003552.A12850@redhat.com>; from bcrl@redhat.com on Mon, Jan 21, 2002 at 12:35:52AM -0500
On Mon, Jan 21, 2002 at 12:35:52AM -0500, Benjamin LaHaise wrote:
> On Mon, Jan 21, 2002 at 02:12:24AM +0100, Andrea Arcangeli wrote:
> > yes, in short the API to allow the userspace to keep the I/O pipeline
> > full with a ring of user buffers is not available at the moment.
>
> See http://www.kvack.org/~blah/aio/ . Seems to work pretty nicely
> for raw io.
of course async-io API is the right fix to keep the I/O pipeline always
full. Thanks for pointing it out.
Andrea
next prev parent reply other threads:[~2002-01-21 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201181743.g0IHhO226012@street-vision.com.suse.lists.linux.kernel>
[not found] ` <3C48607C.35D3DDFF@redhat.com.suse.lists.linux.kernel>
[not found] ` <20020120201603.L21279@athlon.random.suse.lists.linux.kernel>
2002-01-20 21:28 ` performance of O_DIRECT on md/lvm Andi Kleen
2002-01-20 21:42 ` arjan
2002-01-21 1:12 ` Andrea Arcangeli
2002-01-21 5:35 ` Benjamin LaHaise
2002-01-21 14:41 ` Andrea Arcangeli [this message]
[not found] <p734rlg90ga.fsf@oldwotan.suse.de.suse.lists.linux.kernel>
[not found] ` <m16SPj2-000OVeC@amadeus.home.nl.suse.lists.linux.kernel>
2002-01-20 22:11 ` Andi Kleen
2002-01-18 17:43 Justin Cormack
2002-01-18 17:50 ` Arjan van de Ven
2002-01-20 19:16 ` Andrea Arcangeli
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=20020121154125.A8292@athlon.random \
--to=andrea@suse.de \
--cc=ak@suse.de \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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