linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Malahal Naineni <malahal@us.ibm.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFS Mount Option 'nofsc'
Date: Thu, 9 Feb 2012 08:48:13 -0600	[thread overview]
Message-ID: <20120209144812.GA15569@us.ibm.com> (raw)
In-Reply-To: <1328766702.8981.106.camel@serendib>

Harshula [harshula@redhat.com] wrote:
> Hi Trond,
> 
> Thanks for the reply. Could you please elaborate on the subtleties
> involved that require an application to be rewritten if forcedirectio
> mount option was available?
> 
> On Thu, 2012-02-09 at 04:12 +0000, Myklebust, Trond wrote:
> > On Thu, 2012-02-09 at 14:56 +1100, Harshula wrote:
> > >
> > > The "sync" option, depending on the NFS server, may impact the NFS
> > > server's performance when serving many NFS clients. But still worth a
> > > try.
> > 
> > What on earth makes you think that directio would be any different?
> 
> Like I said, sync is still worth a try. I will do O_DIRECT Vs sync mount
> option runs and see what the numbers look like. A while back the numbers
> for cached Vs direct small random writes showed as the number of threads
> increased the cached performance fell well below direct performance. In
> this case I'll be looking at large streaming writes, so completely
> different scenario, but I'd like to verify the numbers first.

directio and sync behavior should be same on server side, but it would
be a different story on the client though. The above behavior you
described is expected on the client.

Thanks, Malahal.


  reply	other threads:[~2012-02-09 14:49 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 [this message]
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
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=20120209144812.GA15569@us.ibm.com \
    --to=malahal@us.ibm.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).