From: Kenny Simpson <theonetruekenny@yahoo.com>
To: David Lloyd <dmlloyd@tds.net>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Is user-space AIO dead?
Date: Wed, 11 Jan 2006 11:20:56 -0800 (PST) [thread overview]
Message-ID: <20060111192056.67364.qmail@web34113.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0601111304390.14191@tomservo.workpc.tds.net>
--- David Lloyd <dmlloyd@tds.net> wrote:
> On Wed, 11 Jan 2006, Kenny Simpson wrote:
>
> > --- David Lloyd <dmlloyd@tds.net> wrote:
> >> Wouldn't nonblocking I/O on regular files be nice?
> >
> > Yes it could be. As I understand it, regular file writes (not O_DIRECT)
> > are only to the page cache and only block when there is memory pressure
> > (so it is more of a throttle).
>
> If you were however using O_DIRECT or O_SYNC, you would then have a
> mechanism to know when your writes have made it to disk, which might be
> useful for transactional systems.
Right, but I'm not sure O_DIRECT implies stable storage, only data sent out to the device, not
held up in the page cache (I could be wrong).
AIO is implemented for O_DIRECT according to the paper, but they observed it not having benefit.
AIO being implemented to O_SYNC would be nice for my use, as it would also eliminate the extra
alignment restrictions brought on by O_DIRECT.
-Kenny
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-01-11 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 18:12 Kenny Simpson
2006-01-11 18:20 ` Marcin Dalecki
2006-01-11 18:23 ` David Lloyd
2006-01-11 18:45 ` Kenny Simpson
2006-01-11 19:10 ` David Lloyd
2006-01-11 19:20 ` Kenny Simpson [this message]
2006-01-11 20:31 ` Phillip Susi
2006-01-11 22:02 ` Kenny Simpson
2006-01-12 3:50 ` Phillip Susi
2006-01-12 4:14 ` Phillip Susi
2006-01-11 18:41 ` Benjamin LaHaise
2006-01-11 18:54 ` Kenny Simpson
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=20060111192056.67364.qmail@web34113.mail.mud.yahoo.com \
--to=theonetruekenny@yahoo.com \
--cc=dmlloyd@tds.net \
--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
Powered by JetHome