From: <iodophlymiaelo@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: raw aio write guarantee
Date: Wed, 28 Sep 2005 00:12:33 -0700 [thread overview]
Message-ID: <98b62faa050928001275d28771@mail.gmail.com> (raw)
Hi all,
Just a quick question: How can a user-mode application ensure that an
AIO write on a raw block device (i.e. open()ed with O_DIRECT) has
really -really- been written to the disk and not residing in an on-disk
write cache where it could be lost in case of a power failure? Is
physical write guaranteed to have taken place before the AIO
completion? Or is there a system call that sends a cache flush
command to the drive (and waits for the drive to commit)?
next reply other threads:[~2005-09-28 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 7:12 iodophlymiaelo [this message]
2005-09-28 7:57 ` raw aio write guarantee Valdis.Kletnieks
2005-09-28 8:56 ` iodophlymiaelo
2005-09-28 9:23 ` Valdis.Kletnieks
2005-09-28 16:42 ` iodophlymiaelo
2005-09-28 20:13 ` Kyle Moffett
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=98b62faa050928001275d28771@mail.gmail.com \
--to=iodophlymiaelo@gmail.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;
as well as URLs for NNTP newsgroup(s).