From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "J.A. Magallón" <jamagallon@ono.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-nfs@vger.kernel.org
Subject: Re: NFSv4
Date: Fri, 19 Feb 2010 11:19:14 -0800 [thread overview]
Message-ID: <1266607154.3526.30.camel@localhost> (raw)
In-Reply-To: <20100219012322.3d323794@werewolf.home>
On Fri, 2010-02-19 at 01:23 +0100, J.A. Magallón wrote:
> Hi all...
>
> First of all, kudos for new nfs-utils. Now, nfs4 works automagically and
> like a charm.
>
> And now the hard part, some questions:
>
> - I have read that nfs4 includes in the server the locking protocol, no
> need for separate lockd. But in my servers, it seems it is still running:
>
> root 2198 2 0 Feb18 ? 00:00:00 [nfsiod]
> root 23501 2 0 01:01 ? 00:00:00 [nfsd4]
> root 23502 2 0 01:01 ? 00:00:00 [nfsd]
> root 23503 2 0 01:01 ? 00:00:00 [nfsd]
> root 23504 2 0 01:01 ? 00:00:00 [nfsd]
> root 23505 2 0 01:01 ? 00:00:00 [nfsd]
> root 23506 2 0 01:01 ? 00:00:00 [nfsd]
> root 23507 2 0 01:01 ? 00:00:00 [nfsd]
> root 23508 2 0 01:01 ? 00:00:00 [nfsd]
> root 23509 2 0 01:01 ? 00:00:00 [nfsd]
> root 23500 2 0 01:01 ? 00:00:00 [lockd]
>
> Is there any problem with it ? I suppose (correct me if I'm wrong)
> that this kernel lockd will only serve for v2 or v3 mounts,
> that locking for client nfs4 mounts will go through nfsd4.
> Is that right ?
No. The client NFSv4 traffic goes through the ordinary 'nfsd' daemons.
There is no special locking manager for NFSv4, since POSIX locks are
part of the ordinary protocol.
I don't think that the NFS server will switch off lockd even if you do
specify that you only want to serve NFSv4.
> - Why is there only 1 instance of v4 daemon ?
The 'nfsd4' thread above is actually a workqueue that is used for
garbage-cleaning expired NFSv4 state. It isn't a server thread.
> - Is there any page describing the advantages of v4 ? I will have to
> convince the department admin to activate v4 in his solaris boxen...;)
One place to start is the NFSv4 design considerations. See
http://tools.ietf.org/html/rfc2624
Cheers
Trond
prev parent reply other threads:[~2010-02-19 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 0:23 NFSv4 J.A. Magallón
2010-02-19 19:19 ` 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=1266607154.3526.30.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.