cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [NFS] [PATCH 3/4 Revised] NLM - kernel lockd-statd changes
Date: Fri, 13 Apr 2007 15:31:03 -0400	[thread overview]
Message-ID: <461FDA77.5080009@redhat.com> (raw)
In-Reply-To: <20070413191615.GU1804@redhat.com>

Lon Hohberger wrote:
> On Wed, Apr 11, 2007 at 02:50:04PM +1000, Neil Brown wrote:
>   
>> lockd knows which is which either based on the destination network
>> address of the lock request, or the filesystem on which the lock was
>> taken.   Somehow this information needs to get communicated to statd
>> so that different 'sm' directories can be used.  my_name seems a
>> sensible place to put the information.
>>     
>
> Right.  Using the inbound-destination address instead of fsid or file
> system will ensure the right address is used for sending the SM_NOTIFY
> requests.  However, fsid, or export path - on a service with more than
> one network address will not, I think...
>   

So I think we conclude here that inbound-destination address is required 
for SM_NOTIFY purpose.

Thanks for all the comments. Will summarize the issues on Monday and see 
what we should go from there.

-- Wendy



  reply	other threads:[~2007-04-13 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 21:52 [Cluster-devel] [PATCH 3/4 Revised] NLM - kernel lockd-statd changes Wendy Cheng
2007-04-10  9:10 ` [Cluster-devel] Re: [NFS] " Olaf Kirch
2007-04-10 14:41   ` Lon Hohberger
2007-04-10 15:00   ` Wendy Cheng
2007-04-10 18:16   ` Wendy Cheng
     [not found]   ` <message from Olaf Kirch on Tuesday April 10>
2007-04-11  4:50     ` Neil Brown
2007-04-13 19:16       ` Lon Hohberger
2007-04-13 19:31         ` Wendy Cheng [this message]
2007-04-17 11:52         ` Olaf Kirch
2007-04-17 13:24           ` Wendy Cheng
2007-04-17 14:51             ` Olaf Kirch
2007-04-17 15:09               ` Wendy Cheng

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=461FDA77.5080009@redhat.com \
    --to=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;
as well as URLs for NNTP newsgroup(s).