All of lore.kernel.org
 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: Tue, 17 Apr 2007 09:24:35 -0400	[thread overview]
Message-ID: <4624CA93.4040307@redhat.com> (raw)
In-Reply-To: <200704171352.27620.okir@lst.de>

Olaf Kirch wrote:
> On Friday 13 April 2007 21:16, Lon Hohberger wrote:
>   
>> The simplification here is a bit incorrect; we need to be able to handle
>> a given *set* of size >= 1 IPs which is paired with a *set* of size >= 1
>> of fsids.  The sets are not broken up (that is, we won't be moving 
>> file systems between IP addresses or vice-vers), but the number of
>> IPs:filesystems need not be 1:1.
>>
>>    * 1 file system, 1 ip address
>>    * 2 fs, 1 ip
>>    * 1 ip, 2 fs
>>    * 18 ip, 42 fs.
>>     
>
> So you move a bunch of file systems with a bunch of IPs, and that
> information is recorded somewhere. So if you know you're moving
> set X, which goes with IPs 1.2.3.4 and 1.2.3.5, you might as well
> send notifications from both these IPs to all clients having established
> locks on a file system from that set.
>
> I think in term of correctness, it's better to send an SM_NOTIFY
> for each IP associated with such a set, anyway.
>   

That's exactly what we have been proposing... :) .. We'll rely heavily 
on HA callout program to tell us which client uses which (server) 
floating IP. 
> To me, it seems the crucial point of information here when monitoring
> a client, is which file system (or set of file systems) the client has
> accessed.
>
>   
The summary will be sent out shortly ... sorry - it is a little bit 
behind schedules due to other issues.

-- Wendy



WARNING: multiple messages have this Message-ID (diff)
From: Wendy Cheng <wcheng@redhat.com>
To: Olaf Kirch <okir@lst.de>
Cc: Neil Brown <neilb@suse.de>,
	cluster-devel@redhat.com, Lon Hohberger <lhh@redhat.com>,
	nfs@lists.sourceforge.net
Subject: Re: [PATCH 3/4 Revised] NLM - kernel lockd-statd changes
Date: Tue, 17 Apr 2007 09:24:35 -0400	[thread overview]
Message-ID: <4624CA93.4040307@redhat.com> (raw)
In-Reply-To: <200704171352.27620.okir@lst.de>

Olaf Kirch wrote:
> On Friday 13 April 2007 21:16, Lon Hohberger wrote:
>   
>> The simplification here is a bit incorrect; we need to be able to handle
>> a given *set* of size >= 1 IPs which is paired with a *set* of size >= 1
>> of fsids.  The sets are not broken up (that is, we won't be moving 
>> file systems between IP addresses or vice-vers), but the number of
>> IPs:filesystems need not be 1:1.
>>
>>    * 1 file system, 1 ip address
>>    * 2 fs, 1 ip
>>    * 1 ip, 2 fs
>>    * 18 ip, 42 fs.
>>     
>
> So you move a bunch of file systems with a bunch of IPs, and that
> information is recorded somewhere. So if you know you're moving
> set X, which goes with IPs 1.2.3.4 and 1.2.3.5, you might as well
> send notifications from both these IPs to all clients having established
> locks on a file system from that set.
>
> I think in term of correctness, it's better to send an SM_NOTIFY
> for each IP associated with such a set, anyway.
>   

That's exactly what we have been proposing... :) .. We'll rely heavily 
on HA callout program to tell us which client uses which (server) 
floating IP. 
> To me, it seems the crucial point of information here when monitoring
> a client, is which file system (or set of file systems) the client has
> accessed.
>
>   
The summary will be sent out shortly ... sorry - it is a little bit 
behind schedules due to other issues.

-- 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

  reply	other threads:[~2007-04-17 13:24 UTC|newest]

Thread overview: 24+ 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-05 21:52 ` Wendy Cheng
2007-04-10  9:09 ` Olaf Kirch
2007-04-10  9:10   ` [Cluster-devel] Re: [NFS] " Olaf Kirch
2007-04-10 14:41   ` Lon Hohberger
2007-04-10 14:41     ` Lon Hohberger
2007-04-10 15:00   ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2007-04-10 15:00     ` Wendy Cheng
2007-04-10 18:16   ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2007-04-10 18:16     ` Wendy Cheng
     [not found]   ` <message from Olaf Kirch on Tuesday April 10>
2007-04-11  4:50     ` [Cluster-devel] Re: [NFS] " Neil Brown
2007-04-11  4:50       ` Neil Brown
2007-04-13 19:16       ` [Cluster-devel] Re: [NFS] " Lon Hohberger
2007-04-13 19:16         ` Lon Hohberger
2007-04-13 19:31         ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2007-04-13 19:31           ` Wendy Cheng
2007-04-17 11:52         ` [Cluster-devel] Re: [NFS] " Olaf Kirch
2007-04-17 11:52           ` Olaf Kirch
2007-04-17 13:24           ` Wendy Cheng [this message]
2007-04-17 13:24             ` Wendy Cheng
2007-04-17 14:51             ` [Cluster-devel] Re: [NFS] " Olaf Kirch
2007-04-17 14:51               ` Olaf Kirch
2007-04-17 15:09               ` [Cluster-devel] Re: [NFS] " Wendy Cheng
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=4624CA93.4040307@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 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.