From: Derek McEachern <derekm@ti.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS Mount Option 'nofsc'
Date: Wed, 8 Feb 2012 12:13:23 -0600 [thread overview]
Message-ID: <4F32BB43.6040209@ti.com> (raw)
In-Reply-To: <1328676860.2954.9.camel@lade.trondhjem.org>
-------- Original Message --------
Subject: Re: NFS Mount Option 'nofsc'
From: Myklebust, Trond <Trond.Myklebust@netapp.com>
To: Derek McEachern <derekm@ti.com>
CC: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Date: Tuesday, February 07, 2012 10:55:04 PM
> On Tue, 2012-02-07 at 20:45 -0600, Derek McEachern wrote:
>> I joined the mailing list shortly after Neil sent out a request for
>> volunteer to update the nfs man page documenting the 'fsc'/'nofsc'
>> options. I suspect this may stem from a ticket we opened with Suse
>> inquiring about these options.
>>
>> Coming from a Solaris background we typically use the 'forcedirectio'
>> option for certain mounts and I was looking for the same thing in Linux.
>> The typically advice seems to be use 'noac' but the description in the
>> man page doesn't seem to match what I would expect from 'forcedirectio',
>> namely no buffering on the client.
>>
>> Poking around the kernel I found the 'fsc'/'nofsc' options and my
>> question is does 'nofsc' provide 'forcedirectio' functionality?
> No. There is no equivalent to the Solaris "forcedirectio" mount option
> in Linux.
> Applications that need to use uncached i/o are required to use the
> O_DIRECT open() mode instead, since pretty much all of them need to be
> rewritten to deal with the subtleties involved anyway.
>
> Trond
So then what exact functionality if provided by the 'nofsc' option? It
would seem to me from a write perspective that between noac and the sync
option it is pretty close to forcedirectio.
From the man page describing sync "any system call that writes data to
files on that mount point causes that data to be flushed to the server
before the system call returns control to user space."
Maybe I've answered one of my questions as flushing the data to the
server before returning to user space is really what I'm after. The
userspace app should be blocked until the write has been acknowledged by
the server and if the server is an NFS appliance then I don't
necessarily care if it has committed the data to disk as I expect it to
managed its cache properly.
Though I still want to understand what 'nofsc' is doing.
Derek
next prev parent reply other threads:[~2012-02-08 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 2:45 NFS Mount Option 'nofsc' Derek McEachern
2012-02-08 4:55 ` Myklebust, Trond
2012-02-08 7:43 ` Harshula
2012-02-08 15:40 ` Chuck Lever
2012-02-09 3:56 ` Harshula
2012-02-09 4:12 ` Myklebust, Trond
2012-02-09 5:51 ` Harshula
2012-02-09 14:48 ` Malahal Naineni
2012-02-09 15:31 ` Myklebust, Trond
2012-02-10 8:07 ` Harshula
2012-02-10 16:48 ` Myklebust, Trond
2012-02-20 5:35 ` Harshula
2012-02-08 18:13 ` Derek McEachern [this message]
2012-02-08 18:15 ` Chuck Lever
2012-02-08 19:52 ` Derek McEachern
2012-02-08 20:00 ` Chuck Lever
2012-02-08 21:16 ` Derek McEachern
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=4F32BB43.6040209@ti.com \
--to=derekm@ti.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).