From: Tom Vier <thomassr@erols.com>
To: Denis Perchine <dyp@perchine.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: O_DSYNC flag for open
Date: Wed, 14 Mar 2001 22:26:42 -0500 [thread overview]
Message-ID: <20010314222642.A19634@zero> (raw)
In-Reply-To: <01031013035702.00608@dyp.perchine.com>
In-Reply-To: <01031013035702.00608@dyp.perchine.com>; from dyp@perchine.com on Sat, Mar 10, 2001 at 01:03:57PM +0600
fdatasync() is the same as fsync(), in linux. until fdatasync() is
implimented (ie, syncs the data only), there's no reason to define O_DSYNC.
just use:
#ifndef O_DSYNC
# define O_DSYNC O_SYNC
#endif
On Sat, Mar 10, 2001 at 01:03:57PM +0600, Denis Perchine wrote:
> one small question... Will O_DSYNC flag be available in Linux?
> It is available at least on AIX, and HP-UX. The difference with O_SYNC is the
> same as between fsync and fdatasync.
--
Tom Vier <thomassr@erols.com>
DSA Key id 0x27371A2C
next prev parent reply other threads:[~2001-03-15 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-10 7:03 O_DSYNC flag for open Denis Perchine
2001-03-15 3:26 ` Tom Vier [this message]
2001-03-16 12:11 ` Stephen C. Tweedie
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=20010314222642.A19634@zero \
--to=thomassr@erols.com \
--cc=dyp@perchine.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