From: "Steve Graegert" <graegerts@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: FILE_FLAG_WRITE_THROUGH
Date: Wed, 5 Apr 2006 09:36:25 +0200 [thread overview]
Message-ID: <6a00c8d50604050036p127a1348hee9c6fa7ea67bed@mail.gmail.com> (raw)
In-Reply-To: <20060405065038.GB716@ju.Imrashi.net.bd>
On 4/5/06, Progga <abulfazl@juniv.edu> wrote:
> On Wed, Apr 05, 2006 at 05:02:20AM +0100, Glynn Clements wrote:
>
> > The O_DIRECT flag suggested by Steve is probably overkill. It requires
> > that the buffer start address, buffer size and file offset are all
> > multiples of the filesystem's block size, and only works on some
> > filesystems.
>
> Although it works for a single file, how good is fsync() in this case?
fsync(2) does not ensure that all data has actually been written to
disk. The controller may indicate that all data is stable, but it
does so even if it is still in its internal cache. From this point of
view, fsync(2) is not a replacement for O_DIRECT.
\Steve
next prev parent reply other threads:[~2006-04-05 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 17:53 FILE_FLAG_WRITE_THROUGH Rebelde
2006-04-04 19:13 ` FILE_FLAG_WRITE_THROUGH Steve Graegert
2006-04-05 4:02 ` FILE_FLAG_WRITE_THROUGH Glynn Clements
2006-04-05 6:50 ` FILE_FLAG_WRITE_THROUGH Progga
2006-04-05 7:36 ` Steve Graegert [this message]
2006-04-05 18:47 ` FILE_FLAG_WRITE_THROUGH Glynn Clements
2006-04-06 7:02 ` FILE_FLAG_WRITE_THROUGH Steve Graegert
2006-04-05 7:31 ` FILE_FLAG_WRITE_THROUGH Steve Graegert
2006-04-05 13:43 ` FILE_FLAG_WRITE_THROUGH Al Boldi
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=6a00c8d50604050036p127a1348hee9c6fa7ea67bed@mail.gmail.com \
--to=graegerts@gmail.com \
--cc=linux-c-programming@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).