From: Olaf Kirch <okir@suse.de>
To: nhorman@redhat.com
Cc: nfs@lists.sourceforge.net
Subject: Re: [RFC] implementing BSD style locks on NLM (flocks)
Date: Wed, 2 Mar 2005 16:56:35 +0100 [thread overview]
Message-ID: <20050302155634.GE22736@suse.de> (raw)
In-Reply-To: <20050227192113.GA5778@localhost.localdomain>
Hi,
> I was wondering, how much interest there might be in the addition of
> support for BSD style locks (flocks) over NLM. I was thinking that a bit could
> be added to differentiate the two namespaces. Any thoughts appreciated.
I looked into this before, and it's not just two "name spaces". The major
difference is that BSD flocks are associated with an open file handle,
while POSIX locks are associated with a PID.
You could possibly encode the notion of a struct file in the owner
handle that's passed in every lock request, and change the server side
lockd when comparing lock owners.
But I dimly remember there were other issues that could not be mapped
easily to the NLM protocol... don't remember the details: I'd have to
check my archives. These mails may even be in the nfs list archive.
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-02 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 19:21 [RFC] implementing BSD style locks on NLM (flocks) nhorman
2005-03-02 15:56 ` Olaf Kirch [this message]
2005-03-02 18:10 ` Trond Myklebust
2005-03-02 18:44 ` Olaf Kirch
2005-03-02 18:55 ` Trond Myklebust
2005-03-03 18:24 ` nhorman
2005-03-03 21:19 ` Trond Myklebust
2005-03-14 15:29 ` Trond Myklebust
2005-03-04 15:02 ` statd -o change G. Allen Morris III
2005-03-04 15:34 ` G. Allen Morris III
2005-03-04 19:48 ` Trond Myklebust
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=20050302155634.GE22736@suse.de \
--to=okir@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=nhorman@redhat.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 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.