linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Mi Jinlong <mijinlong@cn.fujitsu.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFSV4 :All lock operations should be sent to the server for resolution
Date: Mon, 28 Nov 2011 10:42:13 -0500	[thread overview]
Message-ID: <1322494933.6125.21.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4ED32AAB.8010800@cn.fujitsu.com>

On Mon, 2011-11-28 at 14:31 +0800, Mi Jinlong wrote: 
> Hi Trond,
> 
> Trond Myklebust:
> > The ability to cache locks is one of the main reasons for holding
> > delegations in the first place. Sure, the spec allows for non-posix
> > locking, but the Linux client doesn't.
> 
>   Would you mind tell me some about why we not support non-posix locking at NFS ?

For the very obvious reason that Linux applications are coded under the
assumption that the kernel implements POSIX locking semantics. Why would
we want to implement support for NFS features that can cause perfectly
correctly coded applications to hang and crash?

Trond

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com


      reply	other threads:[~2011-11-28 15:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14  6:45 [PATCH] NFSV4 :All lock operations should be sent to the server for resolution Fu Liankun
2011-01-14 18:16 ` J. Bruce Fields
2011-01-14 18:29   ` Trond Myklebust
2011-11-28  6:31     ` Mi Jinlong
2011-11-28 15:42       ` 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=1322494933.6125.21.camel@lade.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mijinlong@cn.fujitsu.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).