Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 delegations criteria? Fwd: Tuning Linux NFSv4 for high latency connections?
Date: Tue, 8 Jul 2014 10:47:57 -0400	[thread overview]
Message-ID: <20140708144757.GA23212@fieldses.org> (raw)
In-Reply-To: <CALXu0Uf9XOoZk8LQPcktWr=i6SAe903O0eLQYiLTFNWx=vxY=g@mail.gmail.com>

On Mon, Jul 07, 2014 at 06:24:41PM +0200, Cedric Blancher wrote:
> Anyone?
> 
> Ced
> 
> On 23 April 2014 23:03, Cedric Blancher <cedric.blancher@gmail.com> wrote:
> > What are the criteria for grating a file delegation in NFSv4?

They're generally implementation-specific.

> > Are file
> > delegations retained even if a process closes a file and the next
> > process in the chain opens it again (e.g. in a shell script)?

Yes, they can be.

> >
> > Ced
> >
> > PS: Who again grants NFSv4 delegations? Server or client?

The server.

> > Do
> > delegations work when data are appended at the end of a file?

The holder of a write delegation can append, yes.

The rfc's (3530 and 5661) have some more details.

I suspect the Solaris server supports write delegations.  The Linux
server doesn't.

Hard to tell the reason for the performance difference you describe,
though, you'd probably need to gather some statistics.

--b.

> >
> > ---------- Forwarded message ----------
> > From: Cedric Blancher <cedric.blancher@gmail.com>
> > Date: 23 April 2014 20:01
> > Subject: Tuning Linux NFSv4 for high latency connections?
> > To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
> >
> >
> > Are there any options to improve the Linux NFSv4 performance over a
> > high latency connection?
> >
> > We currently use Solaris/Illumos as NFSv4 server and client over a
> > cross continental Internet connection. Latency is terrible (~220ms)
> > but the counter this by running work in parallel so the latency is
> > mostly mitigated.
> >
> > We now wish to migrate (short: Away from Oracle because support is
> > basically unbearable) to Linux (tested SuSE 13.1 and current Fedora)
> > and build times are 17 times (!!!) SLOWER than on Solaris/Illumos.
> >
> > Are there any tunables besides actimeo=300?
> >
> > Ced
> > --
> > Cedric Blancher <cedric.blancher@gmail.com>
> > Institute Pasteur
> >
> >
> > --
> > Cedric Blancher <cedric.blancher@gmail.com>
> > Institute Pasteur
> 
> 
> 
> -- 
> Cedric Blancher <cedric.blancher@gmail.com>
> Institute Pasteur
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2014-07-08 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 21:03 NFSv4 delegations criteria? Fwd: Tuning Linux NFSv4 for high latency connections? Cedric Blancher
2014-07-07 16:24 ` Cedric Blancher
2014-07-08 14:47   ` J. Bruce Fields [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=20140708144757.GA23212@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=cedric.blancher@gmail.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