From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Kums <kumaran.rajaram@gmail.com>
Cc: Moazam Raja <moazam@gmail.com>, linux-nfs@vger.kernel.org
Subject: Re: O_DIRECT, O_SYNC, or fsync() on NFS mounts?
Date: Mon, 22 Nov 2010 13:04:51 -0500 [thread overview]
Message-ID: <1290449091.2909.0.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <AANLkTikFfdMWs0b4V1doVYUx1T96+ef8-dMUZf3v8cW9@mail.gmail.com>
On Mon, 2010-11-22 at 10:45 -0700, Kums wrote:
> On Sat, Nov 20, 2010 at 4:54 PM, Trond Myklebust <trond.myklebust@fys.uio.no
> > wrote:
> > If so, then that would be
> > a much stronger guarantee than POSIX and local disk give you, and it
> > will seriously impact I/O performance (whether you use NFS, local disk
> > or whatever).
> >
>
> Yes, I understand. Iam just throwing out a suggestion to see if "-o sync"
> nfs mount + sync exportfs option can be alternative to using O_SYNC or
> O_DIRECT in the application (to guarantee everything written by application
> hits the disk).
mount -osync under NFS works exactly the same as under any other
filesystem, so yes...
Trond
prev parent reply other threads:[~2010-11-22 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 23:34 O_DIRECT, O_SYNC, or fsync() on NFS mounts? Moazam Raja
2010-11-19 19:24 ` Trond Myklebust
2010-11-19 19:55 ` Chuck Lever
2010-11-19 20:04 ` J. Bruce Fields
2010-11-19 21:26 ` Trond Myklebust
2010-11-19 21:48 ` J. Bruce Fields
2010-11-21 10:46 ` Christoph Hellwig
2010-11-21 19:31 ` Moazam Raja
2010-11-21 20:01 ` Trond Myklebust
[not found] ` <AANLkTi=AV20AsUKOGfVg6M92T8LfPLuuyrG_hQESw_RU@mail.gmail.com>
2010-11-20 23:54 ` Trond Myklebust
[not found] ` <AANLkTikFfdMWs0b4V1doVYUx1T96+ef8-dMUZf3v8cW9@mail.gmail.com>
2010-11-22 18:04 ` Trond Myklebust [this message]
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=1290449091.2909.0.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=kumaran.rajaram@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=moazam@gmail.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;
as well as URLs for NNTP newsgroup(s).