public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: 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 07:47:37 -0400	[thread overview]
Message-ID: <20100527114736.GA13112@infradead.org> (raw)
In-Reply-To: <4BFD3926.6040208@hardwarefreak.com>

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.

I have no idea why the MTAs don't want to use it - it's generally easier
to use then memory mapped I/O, and has much more deterministic
performance.

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

  parent reply	other threads:[~2010-05-27 11:45 UTC|newest]

Thread overview: 23+ 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 10:18 ` Dave Chinner
2010-05-23 14:23   ` Roman Kononov
2010-05-24  1:19     ` Dave Chinner
2010-06-12  5:00       ` Ilia Mirkin
2010-06-13 22:47         ` Dave Chinner
2010-06-13 23:10           ` Ilia Mirkin
2010-06-14  1:29             ` Dave Chinner
2010-06-14  3:27               ` Ilia Mirkin
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 [this message]
2010-05-27 13:58               ` Stewart Smith
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=20100527114736.GA13112@infradead.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox