From: "Frank Filz" <ffilzlnx@mindspring.com>
To: "'J. Bruce Fields'" <bfields@fieldses.org>,
"'Brian Cowan'" <brian.cowan@hcl.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: RE: 2 potentially stupid questions.
Date: Mon, 26 Jun 2017 16:24:35 -0700 [thread overview]
Message-ID: <007e01d2eed3$638534b0$2a8f9e10$@mindspring.com> (raw)
In-Reply-To: <20170626221233.GA2186@fieldses.org>
Have you added nfs-ganesha to your list of servers?
> -----Original Message-----
> From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-
> owner@vger.kernel.org] On Behalf Of J. Bruce Fields
> Sent: Monday, June 26, 2017 3:13 PM
> To: Brian Cowan <brian.cowan@hcl.com>
> Cc: linux-nfs@vger.kernel.org
> Subject: Re: 2 potentially stupid questions.
>
> On Mon, Jun 26, 2017 at 09:09:49PM +0000, Brian Cowan wrote:
> > The "feature implemented only in linux" statement worries me... Does
> > this mean that only Linux's NFS client server implements this NFSv4.1
> > "lock freed" behavior?
>
> Actually, I shouldn't have said that. The linux (client and server)
> implementation is the one I know of, but there may well be others. It's
an
> optional feature of NFSv4.1:
>
> https://tools.ietf.org/html/rfc5661#section-20.11
>
> If you notice 1-second-ish delays acquiring contended locks against other
> servers then it may be worth filing bugs with them and suggesting they
> support CB_NOTIFY_LOCK. It shouldn't be especially difficult.
Adding that support to nfs-ganesha is on our todo list...
Frank
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2017-06-27 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PS1PR04MB1692ED9241F275897AC5F320FEDB0@PS1PR04MB1692.apcprd04.prod.outlook.com>
2017-06-22 18:51 ` 2 potentially stupid questions Brian Cowan
2017-06-23 16:06 ` J. Bruce Fields
2017-06-24 0:42 ` Brian Cowan
2017-06-26 17:38 ` J. Bruce Fields
2017-06-26 21:09 ` Brian Cowan
2017-06-26 22:12 ` J. Bruce Fields
2017-06-26 23:24 ` Frank Filz [this message]
[not found] ` <PS1PR04MB1692E34FE8FEFC1CB28D4F5AFEDC0@PS1PR04MB1692.apcprd04.prod.outlook.com>
2017-06-27 14:00 ` Brian Cowan
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='007e01d2eed3$638534b0$2a8f9e10$@mindspring.com' \
--to=ffilzlnx@mindspring.com \
--cc=bfields@fieldses.org \
--cc=brian.cowan@hcl.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