Linux NFS development
 help / color / mirror / Atom feed
From: Malte Cornils <malte@cornils.net>
To: nfs@lists.sourceforge.net
Cc: admin@usta.de
Subject: NFS locking and OpenBSD
Date: Mon, 31 Jan 2005 23:02:30 +0100	[thread overview]
Message-ID: <200501312302.30778.malte@cornils.net> (raw)

Hello,

since OpenBSD as NFS-server supports only NLM 1,2,3. Linux clients with no 
specific mount options use NFS version 3. However, Linux uses NLM version 4 
with that (fs/lockd/nlmclnt_proc.c, line 113 in 2.6.8).

When set to nfsvers=2, it works, but NFS 2 is (too) slow due to caching etc.

Could we simply set NLM locking version to 1 in the source code 
unconditionally (even for NFS version 3) and expect NFS to work (i.e. is NFS 
protocol 3 able to use older NLM versions than 4)? Of course, I only expect 
an answer from the Linux point of view.

-Malte

BTW, I've tried to search the mailing list archives but only found a post from 
2002 with no answer. 

(BTW, anyone using KDE on NFS-mounted homedirs? The problem occurs in the 
startup phase in kded (when the second icon in the splash blinks) at first 
login. On a local file system, the login is 20-30 seconds faster than on our 
NFS-mounted homedirs)


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2005-01-31 22:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200501312302.30778.malte@cornils.net \
    --to=malte@cornils.net \
    --cc=admin@usta.de \
    --cc=nfs@lists.sourceforge.net \
    /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