From: Chuck Lever <chuck.lever@oracle.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Status of NFS over IPv6
Date: Fri, 29 Jun 2007 18:01:55 -0400 [thread overview]
Message-ID: <46858153.8060109@oracle.com> (raw)
In-Reply-To: <20070629123747.GA1034@uio.no>
[-- Attachment #1: Type: text/plain, Size: 2241 bytes --]
Steinar H. Gunderson wrote:
> What's the current status of NFS over IPv6 in Linux? There are HOWTOs out
> there, but most patches seem to be against old kernel versions, and
> completely unable to run both client and server from the same kernel tree.
> Additionally, I see mentions of replacements for portmap, but no clear
> upstream URL or updated versions anywhere. Also, there seems to be a separate
> git tree maintained by Chuck Lever, but gitweb hides any special patches it
> might have in tons of upstream patches.
>
> I'd very much like to be able to sew all of this together at some point,
> but it's very hard to get a decent overview of it all. Does anyone have a
> "current status" or "plans for the near feature" summary?
I have some patches that add IPv6 support in the RPC client. The server
is more complicated (how to deal with address-based export rules, and so
on). There hasn't been much progress on the server side, but I think
Bull is still working on that.
There are some patches for the NFS client, but we need to have both RPC
client and server support for NFSv4 callback and NLM to work over IPv6
(required for even a complete client implementation).
At this very moment I'm working on implementing mount option parsing in
the kernel so we can easily add IPv6 addressing support to the NFS mount
interface (among other improvements this will enable).
Steve Dickson has added Bull's rpcbind (replacement for portmap) to
Fedora 7, but there is some disagreement about whether to use a complete
replacement, like rpcbind, or whether to add the needed support to the
existing portmap code, in general.
Bull has announced a test plan for user-space RPC libraries, although I
haven't had a moment to look through it. Bull should be providing
testing resources once we have all of this integrated.
While there is some interest in IPv6 among some of Linux's corporate
sponsors, there really isn't an overwhelming "killer" requirement for
IPv6, so there isn't much motivation to get all this completed. I have
to admit I'm pretty burned out on all this because of how complicated it
has all become. I'd be happy if someone stepped forward and volunteered
to help or take over the integration.
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 291 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
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel/
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-06-29 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 12:37 Status of NFS over IPv6 Steinar H. Gunderson
2007-06-29 22:01 ` Chuck Lever [this message]
2007-06-29 22:27 ` Steinar H. Gunderson
2007-07-02 9:36 ` Aurélien Charbon
2007-07-02 11:33 ` [NFS] " Le Rouzic
2007-07-02 16:23 ` Chuck Lever
2007-07-23 12:26 ` Le Rouzic
2007-07-26 7:43 ` Prasad P
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=46858153.8060109@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.