All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@flamingspork.com>
To: Christoph Hellwig <hch@infradead.org>,
	Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: NOW: o_direct   --  WAS: Re: WARNING in xfs_lwr.c, xfs_write()
Date: Thu, 27 May 2010 23:58:55 +1000	[thread overview]
Message-ID: <87pr0hbg4g.fsf@willster.local.flamingspork.com> (raw)
In-Reply-To: <20100527114736.GA13112@infradead.org>

On Thu, 27 May 2010 07:47:37 -0400, Christoph Hellwig <hch@infradead.org> wrote:
> O_DIRECT is not a Posix standard and not very portable.  It originated
> on IRIX, and Linux inherited it during the 2.4 kernel series days.
> These days FreeBSD/NetBSD and AIX support it as well, but for example
> Solaris, HP-UX and OpenBSD don't, nevermind Windows or Mac OS.

There is O_DIRECT type functionality available on Windows, with similar
restrictions for aligned IO too. You have to use the Win32 APIs to do it
though, the POSIX ones won't get you it (or more than 2048 files open at
once).

In practice we've only ever found Solaris (other than linux) to be
reliable with O_DIRECT (at least on UFS... ZFS is... well... I wouldn't
run a database server on it yet).

-- 
Stewart Smith

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-05-27 13:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-23  5:20 WARNING in xfs_lwr.c, xfs_write() Roman Kononov
2010-05-23  5:20 ` Roman Kononov
2010-05-23 10:18 ` Dave Chinner
2010-05-23 10:18   ` Dave Chinner
2010-05-23 14:23   ` Roman Kononov
2010-05-23 14:23     ` Roman Kononov
2010-05-24  1:19     ` Dave Chinner
2010-05-24  1:19       ` Dave Chinner
2010-06-12  5:00       ` Ilia Mirkin
2010-06-12  5:00         ` Ilia Mirkin
2010-06-13 22:47         ` Dave Chinner
2010-06-13 22:47           ` Dave Chinner
2010-06-13 23:10           ` Ilia Mirkin
2010-06-13 23:10             ` Ilia Mirkin
2010-06-14  1:29             ` Dave Chinner
2010-06-14  1:29               ` Dave Chinner
2010-06-14  3:27               ` Ilia Mirkin
2010-06-14  3:27                 ` Ilia Mirkin
2010-06-14 15:11                 ` Roman Kononov
2010-06-14 15:11                   ` Roman Kononov
2010-05-24  4:12     ` Stan Hoeppner
2010-05-24  5:16       ` Stewart Smith
2010-05-24 19:34       ` Roman Kononov
2010-05-26  7:06         ` Dave Chinner
2010-05-26 15:07           ` NOW: o_direct -- WAS: " Stan Hoeppner
2010-05-27 11:05             ` Michael Monnerie
2010-05-27 11:47             ` Christoph Hellwig
2010-05-27 13:58               ` Stewart Smith [this message]
2010-05-27 14:57                 ` Christoph Hellwig
2010-05-27 15:45                   ` Stewart Smith
2010-05-28  0:25               ` Stan Hoeppner
2010-05-27 14:05             ` Stewart Smith
2010-05-28  0:42               ` Stan Hoeppner

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=87pr0hbg4g.fsf@willster.local.flamingspork.com \
    --to=stewart@flamingspork.com \
    --cc=hch@infradead.org \
    --cc=stan@hardwarefreak.com \
    --cc=xfs@oss.sgi.com \
    /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.