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] [RFC PATCH 1/3] NLM lock failover - lock release
Date: Thu, 29 Jun 2006 17:49:04 -0400	[thread overview]
Message-ID: <44A44AD0.7080506@redhat.com> (raw)
In-Reply-To: <76bd70e30606291211t338164adq985e43726da51e59@mail.gmail.com>

Chuck Lever wrote:

>On 6/29/06, Wendy Cheng <wcheng@redhat.com> wrote:
>  
>
>>The patch piggy-backs the logic into "rq_daddr" field of struct svc_rqst
>>where NFS server ip address is stored. Upon writing IPv4 address in
>>standard dot notation into /proc/fs/nfsd/nlm_unlock, the logic will
>>examine NLM's global nlm_files list and subsequently unlock the
>>associated file if server ip address matches.
>>
>>Due to the size of rq_daddr (u32), we would not be able to support IPV6
>>for this round of changes. Another to-do item is to enable client:server
>>ip pairs to allow NFS V4 failover.
>>    
>>
>
>FYI: I have a patch in my IPv6 patchset that increases the size of
>this field specifically in order to hold an IPv6 address.  See:
>
>   http://oss.oracle.com/~cel/linux-2.6/2.6.17/patches/52-svc-rq_daddr.diff
>
>for the individual patch, and surrounding patches for more context.
>
>  
>
ok, thanks ...

-- Wendy

-- 
S. Wendy Cheng
wcheng at redhat.com



  reply	other threads:[~2006-06-29 21:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 18:11 [Cluster-devel] [RFC PATCH 1/3] NLM lock failover - lock release Wendy Cheng
2006-06-29 19:11 ` [Cluster-devel] Re: [NFS] " Chuck Lever
2006-06-29 21:49   ` Wendy Cheng [this message]
2006-06-29 23:06 ` Trond Myklebust
2006-06-30  3:57   ` Wendy Cheng
     [not found]     ` <message from Wendy Cheng on Thursday June 29>
2006-06-30  4:15       ` Neil Brown
2006-06-30  4:38         ` Trond Myklebust
     [not found]           ` <message from Trond Myklebust on Friday June 30>
2006-06-30  5:00             ` Neil Brown
2006-06-30  4:39     ` 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=44A44AD0.7080506@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).