From: Wendy Cheng <wcheng@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: nfs@lists.sourceforge.net, linux clustering <linux-cluster@redhat.com>
Subject: Re: [NFS] [RFC] NLM lock failover admin interface
Date: Mon, 12 Jun 2006 11:44:55 -0400 [thread overview]
Message-ID: <448D8BF7.7010105@redhat.com> (raw)
In-Reply-To: <20060612150053.GC31596@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
J. Bruce Fields wrote:
>On Mon, Jun 12, 2006 at 01:25:43AM -0400, Wendy Cheng wrote:
>
>
>>2. Adding a new flag into "exportfs" command, say "h", such that
>>
>> "exportfs -uh *:/export_path"
>>
>>would un-export the entry and drop the NLM locks associated with the
>>entry.
>>
>>
>
>What does the kernel interface end up looking like in that case?
>
>
>
Happy to see this new exportfs command gets positive response - it was
our original pick too.
Uploaded is part of a draft version of 2.4 base kernel patch - we're
cleaning up 2.6 patches at this moment. It basically adds a new export
flag (NFSEXP_FOLOCK - note that ex_flags is an int but is currently only
defined up to 16 bits) so nfs-util and kernel can communicate.
The nice thing about this approach is the recovery part - the take-over
server can use the counter part command to export and set grace period
for one particular interface within the same system call.
-- Wendy
[-- Attachment #2: gfs_nlm.patch --]
[-- Type: text/plain, Size: 785 bytes --]
--- linux-2.4.21-43.EL/fs/nfsd/export.c 2006-05-14 17:16:21.000000000 -0400
+++ linux/fs/nfsd/export.c 2006-05-29 02:13:29.000000000 -0400
@@ -388,6 +388,10 @@ exp_unexport(struct nfsctl_export *nxp)
exp_do_unexport(exp);
err = 0;
}
+ if (nxp->ex_flags & NFSEXP_FOLOCK) {
+ dprintk("exp_unexport: nfsd_lockd_unexport called\n");
+ nfsd_lockd_unexport(clp);
+ }
}
exp_unlock();
--- linux-2.4.21-43.EL/include/linux/nfsd/export.h 2006-05-14 17:23:57.000000000 -0400
+++ linux/include/linux/nfsd/export.h 2006-05-29 02:12:07.000000000 -0400
@@ -42,7 +42,7 @@
#define NFSEXP_FSID 0x2000
#define NFSEXP_NOACL 0x8000 /* turn off acl support */
#define NFSEXP_ALLFLAGS 0xFFFF
-
+#define NFSEXP_FOLOCK 0x00010000 /* NLM lock failover */
#ifdef __KERNEL__
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-06-12 15:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 5:25 [RFC] NLM lock failover admin interface Wendy Cheng
2006-06-12 6:11 ` Wendy Cheng
2006-06-12 15:00 ` [Linux-cluster] " J. Bruce Fields
2006-06-12 15:44 ` Wendy Cheng [this message]
2006-06-12 16:20 ` Madhan P
2006-06-12 16:58 ` Madhan P
2006-06-12 18:09 ` [NFS] " Wendy Cheng
2006-06-12 17:23 ` [Linux-cluster] " Steve Dickson
2006-06-12 17:27 ` James Yarbrough
2006-06-12 19:07 ` [NFS] " Wendy Cheng
2006-06-13 3:17 ` Neil Brown
2006-06-13 7:00 ` [NFS] " Wendy Cheng
2006-06-13 7:08 ` Neil Brown
2006-06-14 6:54 ` [NFS] " Wendy Cheng
2006-06-14 11:36 ` Christoph Hellwig
2006-06-14 13:39 ` Wendy Cheng
2006-06-14 14:00 ` Wendy Cheng
2006-06-15 14:07 ` [NFS] " William A.(Andy) Adamson
2006-06-15 15:09 ` Wendy Cheng
2006-06-16 6:09 ` [Linux-cluster] " Neil Brown
2006-06-16 15:39 ` [NFS] " William A.(Andy) Adamson
2006-06-15 4:27 ` [NFS] " Neil Brown
2006-06-15 6:39 ` Wendy Cheng
2006-06-15 8:02 ` Neil Brown
2006-06-15 18:43 ` Wendy Cheng
2006-06-13 15:23 ` James Yarbrough
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=448D8BF7.7010105@redhat.com \
--to=wcheng@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-cluster@redhat.com \
--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