From: "Aurélien Charbon" <aurelien.charbon@ext.bull.net>
To: chuck.lever@oracle.com
Cc: NFSv4 ML <nfsv4@linux-nfs.org>,
nfs@lists.sourceforge.net,
"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: Status of NFS over IPv6
Date: Mon, 02 Jul 2007 11:36:12 +0200 [thread overview]
Message-ID: <4688C70C.2050801@ext.bull.net> (raw)
In-Reply-To: <46858153.8060109@oracle.com>
Chuck Lever wrote:
>>
>> 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.
The latest server patches are on our web page. I have upgraded it.
http://nfsv4.bullopensource.org/patches/ipv6-server/IPv6_patchset.php
It includes missing parts of code. I have started from a 2.6.21 kernel +
Chuck patchset.
I have send them to Bruce few weeks ago. Bruce did you received the URL
of new patches ?
> 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.
>
A student is developing a RPC/TI-RPC test suite. TI-RPC and RPCbind
adoption by the community has been discussed on the mailing list few
weeks ago.
> 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.
We hope the interest of community about IPv6 will grow.
Feel free to send comments on the code.
>-------------------------------------------------------------------------
>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
>
>
--
********************************
Aurelien Charbon
Linux NFSv4 team
Bull SAS
Echirolles - France
http://nfsv4.bullopensource.org/
********************************
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-07-02 9:37 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
2007-06-29 22:27 ` Steinar H. Gunderson
2007-07-02 9:36 ` Aurélien Charbon [this message]
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=4688C70C.2050801@ext.bull.net \
--to=aurelien.charbon@ext.bull.net \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
/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