From: Mike Frysinger <vapier@gentoo.org>
To: Neil Brown <neilb@suse.de>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: RFC: merging sm-notify and rpc.statd
Date: Tue, 19 May 2009 19:25:37 -0400 [thread overview]
Message-ID: <200905191925.38902.vapier@gentoo.org> (raw)
In-Reply-To: <18963.13619.563465.804193-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
On Tuesday 19 May 2009 18:39:47 Neil Brown wrote:
> sm-notify :
> - is a 'client' for the "SM" protocol.
> - must be run at boot time, and after that is not needed.
>
> statd :
> - is a 'server' for the "SM" protocol.
> - only needs to be running when either nfsd is running or an
> nfs mount which supports locks is active
that last part -- any nfs mount with locks -- means that pretty much every nfs
client out there needs it running.
sm-notify is pretty minuscule, so the overhead of having that run on a server
is negligible, especially when combined with the already required statd.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-05-19 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 14:36 RFC: merging sm-notify and rpc.statd Chuck Lever
2009-05-19 22:39 ` Neil Brown
[not found] ` <18963.13619.563465.804193-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-05-19 23:25 ` Mike Frysinger [this message]
2009-05-20 1:05 ` NeilBrown
[not found] ` <bdacaae74fbd57ee96599286eae43751.squirrel-eq65iwfR9nKIECXXMXunQA@public.gmane.org>
2009-05-20 1:10 ` Ben Greear
2009-05-20 16:38 ` Chuck Lever
2009-05-21 0:01 ` Neil Brown
[not found] ` <18964.39373.232045.96215-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2009-05-21 17:14 ` Chuck Lever
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=200905191925.38902.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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