Linux NFS development
 help / color / mirror / Atom feed
From: James Yarbrough <jmy@sgi.com>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: cluster-devel@redhat.com, lhh@redhat.com,
	Linux NFS Mailing List <nfs@lists.sourceforge.net>,
	Wendy Cheng <wcheng@redhat.com>
Subject: Re: [PATCH 2/5] NLM failover - per fs grace period
Date: Fri, 18 Aug 2006 13:11:42 -0700	[thread overview]
Message-ID: <44E61EFE.F41140AD@sgi.com> (raw)
In-Reply-To: 1155894561.17651.442.camel@hole.melbourne.sgi.com

Greg Banks wrote:
> 
> On Mon, 2006-08-14 at 16:00, Wendy Cheng wrote:
> > This change enables per NFS-export entry lockd grace period.[...]
> 
> >
> > +/* Server fsid linked list for NLM lock failover */
> > +struct nlm_serv {
> > +     struct nlm_serv*        s_next;         /* linked list */
> > +     unsigned long           s_grace_period; /* per fsid grace period */
> > +     int                     s_fsid;         /* export fsid */
> > +};
> > +
> 
> The name of this structure appears to be left over from your
> previous approach; it doesn't really represent a server anymore.
> Giving the structure, and list, and the lock that protects it
> similar and appropriate names might be nice.
> 
> Also, the s_grace_period field isn't actually a period, it's
> the future expiry time expressed in jiffies.  The field name
> and comment are both confusing.

It might be a good idea to change s_grace_period to something like
s_grace_end since it actually marks the ending time of the grace period.
If you do change the name, it would be a good idea to enhance the
commentary to indicate the relationship of the field to the grace period.
That should leave enough breadcrumbs for anyone familiar with the NLM
terminology to follow.

-- 
jmy@sgi.com
650 933 3124

I need more snakes.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2006-08-18 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14  6:00 [PATCH 2/5] NLM failover - per fs grace period Wendy Cheng
2006-08-14 15:44 ` Trond Myklebust
2006-08-14 15:59   ` Wendy Cheng
2006-08-15 18:32     ` Wendy Cheng
2006-08-18  9:49 ` Greg Banks
2006-08-18 20:11   ` James Yarbrough [this message]

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=44E61EFE.F41140AD@sgi.com \
    --to=jmy@sgi.com \
    --cc=cluster-devel@redhat.com \
    --cc=gnb@melbourne.sgi.com \
    --cc=lhh@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=wcheng@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox