All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Rob van Nieuwkerk <robn@verdi.et.tudelft.nl>
Cc: Andries Brouwer <aebr@win.tue.nl>, Alan Cox <alan@redhat.com>,
	Arjan van de Ven <arjanv@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: open(.. O_DIRECT ..) difference in between Linux and FreeBSD ..
Date: Fri, 13 Jun 2003 07:47:02 +0000	[thread overview]
Message-ID: <20030613074702.B30329@devserv.devel.redhat.com> (raw)
In-Reply-To: <200306122312.h5CNCwhk002147@verdi.et.tudelft.nl>; from robn@verdi.et.tudelft.nl on Fri, Jun 13, 2003 at 01:12:57AM +0200

On Fri, Jun 13, 2003 at 01:12:57AM +0200, Rob van Nieuwkerk wrote:
> FYI:
> It appears that somewhere between RH kernels 2.4.18-27.7.x and 2.4.20-18.9
> something has changed so that my application needs a O_SYNC too besides
> the O_DIRECT to make sure that writes will be synchronous.  If I leave
> the O_SYNC out with 2.4.20-18.9 the write will happen physically 35
> seconds after the write() was done.

O_DIRECT is nothing but a hint and the 2.4.20-18.9 kernel decides to not
honor it

  reply	other threads:[~2003-06-13  7:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-12 11:14 open(.. O_DIRECT ..) difference in between Linux and FreeBSD Matti Aarnio
2003-06-12 11:24 ` Christoph Hellwig
2003-06-12 13:17 ` Andries Brouwer
2003-06-12 14:58   ` Dave Jones
2003-06-12 15:09     ` Matti Aarnio
2003-06-12 23:14       ` Nuno Silva
2003-06-13 21:05       ` Andries Brouwer
2003-06-12 23:12   ` Rob van Nieuwkerk
2003-06-13  7:47     ` Arjan van de Ven [this message]
2003-06-13  8:27       ` Rob van Nieuwkerk
2003-06-13  8:28         ` Arjan van de Ven
2003-06-13  9:02           ` Rob van Nieuwkerk
     [not found] <20030612111437.GE28900@mea-ext.zmailer.org.suse.lists.linux.kernel>
2003-06-12 11:26 ` Andi Kleen

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=20030613074702.B30329@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=aebr@win.tue.nl \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robn@verdi.et.tudelft.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.