From: Andries Brouwer <aebr@win.tue.nl>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: open(.. O_DIRECT ..) difference in between Linux and FreeBSD ..
Date: Thu, 12 Jun 2003 15:17:04 +0200 [thread overview]
Message-ID: <20030612151704.A2588@pclin040.win.tue.nl> (raw)
In-Reply-To: <20030612111437.GE28900@mea-ext.zmailer.org>; from matti.aarnio@zmailer.org on Thu, Jun 12, 2003 at 02:14:37PM +0300
On Thu, Jun 12, 2003 at 02:14:37PM +0300, Matti Aarnio wrote:
> I have been debugging long and hard a thing where IO is done
> with O_DIRECT flag applied to open(2).
>
> Unlike Linux, FreeBSD (where this flag originates, apparently) does
> _not_ require that read()/write() happens from page aligned memory
> areas, and/or be of page-size multiples in size.
>
> This needs at least wording in open(2) man-page
Ha Matti, I was going to suggest you to send a patch to the man page
maintainer, but maybe the wording you ask for is there already and
you just have some outdated version of the manpages?
Andries
O_DIRECT
Try to minimize cache effects of the I/O to and
from this file. In general this will degrade per-
formance, but it is useful in special situations,
such as when applications do their own caching.
File I/O is done directly to/from user space
buffers. The I/O is synchronous, i.e., at the com-
pletion of the read(2) or write(2) system call,
data is guaranteed to have been transferred.
Transfer sizes, and the alignment of user buffer
and file offset must all be multiples of the logi-
cal block size of the file system.
next prev parent reply other threads:[~2003-06-12 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 11:14 Matti Aarnio
2003-06-12 11:24 ` Christoph Hellwig
2003-06-12 13:17 ` Andries Brouwer [this message]
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
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=20030612151704.A2588@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.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
all inboxes | Powered by JetHome®