From: Christoph Hellwig <hch@infradead.org>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Ray Van Dolson <rvandolson@esri.com>,
Nathan Scott <nathans@aconex.com>,
xfs@oss.sgi.com
Subject: Re: O_SYNC behavior?
Date: Tue, 27 Apr 2010 10:12:05 -0400 [thread overview]
Message-ID: <20100427141205.GA557@infradead.org> (raw)
In-Reply-To: <20100427093250.GA15182@citd.de>
On Tue, Apr 27, 2010 at 11:32:50AM +0200, Matthias Schniedermeyer wrote:
> I don't think that answers the intented question.
>
> I guess the correct answer is:
> It depends on the server-side configuration.
> An "async" export gets the "done"-answer immediatly.
> An "sync" export (only when also mounted "sync" AFAIU) waits at least
> until the write command is send down the stack, maybe even until the
> data actually hit the platters or silicon in the SSD-case.
>
> man 5 exports:
> - snip -
> sync: Reply to requests only after the changes have been committed to stable storage
> - snip -
>
> But i guess the performance will be horrible when both side are "sync".
The client side (that is mount-side) sync means implying O_SYNC for all
I/O - no need for that. And sync exports are the default for every sane
server.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-27 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 22:56 O_SYNC behavior? Ray Van Dolson
2010-04-26 23:25 ` Nathan Scott
2010-04-27 9:32 ` Matthias Schniedermeyer
2010-04-27 14:12 ` Christoph Hellwig [this message]
2010-04-27 15:35 ` Ray Van Dolson
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=20100427141205.GA557@infradead.org \
--to=hch@infradead.org \
--cc=ms@citd.de \
--cc=nathans@aconex.com \
--cc=rvandolson@esri.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