From: Wendy Cheng <wcheng@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net, Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: flock and lockf over NFS and the 'pid' in lockd requests.
Date: Mon, 30 Apr 2007 00:11:03 -0400 [thread overview]
Message-ID: <46356C57.1040601@redhat.com> (raw)
In-Reply-To: <17973.26166.844328.279844@notabene.brown>
Neil Brown wrote:
>On Sunday April 29, trond.myklebust@fys.uio.no wrote:
>
>
>>??? On the contrary. Genuine conflicts are currently resolved by the
>>server and the server alone. We do admittedly call do_vfs_lock() with
>>the ACCESS flag set, but that doesn't set a lock.
>>
>Oh bother, I didn't notice the ACCESS setting. Thanks for that.
>
>
Tons of people, including me, missed that flag when they first looked at
this code.
> Indeed... can it be fixed I wonder.
>
>[snip]
>
> - massive rewrite of the lockd code so that the client doesn't depend
> on the server for local arbitration,
>
I "like" this (think about performance gain).
>
>What would you think of an "noflock" option to allow people to choose
>the old practice of not supporting flock???
>
>
Ha! Take easy way out ? (sorry, can't resist this :) ).
-- Wendy
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-04-30 4:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 1:45 flock and lockf over NFS and the 'pid' in lockd requests Neil Brown
2007-04-30 2:13 ` Trond Myklebust
2007-04-30 3:44 ` Neil Brown
2007-04-30 4:11 ` Wendy Cheng [this message]
2007-04-30 4:16 ` Wendy Cheng
2007-04-30 6:08 ` Olaf Kirch
2007-04-30 13:17 ` 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=46356C57.1040601@redhat.com \
--to=wcheng@redhat.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.