All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: need info on IPv6 support for NFS in RHEL and SLES	distros
Date: Wed, 29 Aug 2007 17:16:43 -0400	[thread overview]
Message-ID: <46D5E23B.5080305@oracle.com> (raw)
In-Reply-To: <20070829210828.GA21877@uio.no>

[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]

Steinar H. Gunderson wrote:
> On Wed, Aug 29, 2007 at 12:19:27PM -0400, Chuck Lever wrote:
>> No Linux distribution contains IPv6 support for NFS right now.  The 
>> implementation is still being developed.
> 
> Speaking of which, what's missing now? I see text-based mounts, client-side
> IPv6 RPC and server-side transport switch (of which the first two are already
> in mainline, and the last seems to be on its way) -- my impression was that
> these are all important building blocks. I guess nfs-utils will also need
> some patching, and an IPv6 transport will be needed for plugging into the
> server side transport switch, but after that?

This may be impolitic to say in public, but the transport switch APIs 
aren't really needed for IPv6.  It just seemed easier to apply the IPv6 
changes to the transport switch work than the other way around.

On the client, we will need IPv6 addressing support from the mount.nfs 
command through to the network transport implementations.  We have 
pieces of that implemented.

The client needs to have NFSv4 callback support and lockd support for 
IPv6, so we need RPC server support for IPv6 -- that's nearing 
completion once we have the ip_map cache fixed up to support IPv6 addresses.

On the server, we need support for mountd and rpcbind, and support build 
into the NFS server itself.  I understand Bull is still working on the 
server changes, and SteveD has added rpcbind to Fedora and is making it 
robust.

In addition I think we will need to examine exportfs and anything else 
on the server side to check for any dependence on address format.

To finish, Bull has been testing parts of this work as it has been 
developed, and will need to continue testing it after it has all been 
integrated.  Interoperability testing between Linux, Solaris, and AIX 
are on the list.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 315 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
email;internet:chuck dot lever at nospam oracle dot com
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-08-29 21:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3DFE68BCB5D6994994AA6CB1EC581EA30411E61E@qcaexc02.asiapacific.cpqcorp.net>
2007-08-29 14:33 ` need info on IPv6 support for NFS in RHEL and SLES distros Trond Myklebust
2007-08-29 16:19 ` Chuck Lever
2007-08-29 21:08   ` Steinar H. Gunderson
2007-08-29 21:16     ` Chuck Lever [this message]
2007-08-29 21:18     ` 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=46D5E23B.5080305@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=sgunderson@bigfoot.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.