From: Le Rouzic <aime.le-rouzic@bull.net>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, nfsv4 <nfsv4@linux-nfs.org>
Subject: Re: svc_create_xprt for nfsd and lockd with ipv6
Date: Wed, 28 May 2008 16:56:28 +0200 [thread overview]
Message-ID: <483D729C.307@bull.net> (raw)
In-Reply-To: <DDB646D2-C5B3-4EC3-A8DB-EF7B6F99A8E2@oracle.com>
Chuck Lever a =E9crit :
> On May 26, 2008, at 5:47 AM, Le Rouzic wrote:
>
>> Hi,
>> I was thinking that linux-2.6.25-rc6-CITI_NFS4_ALL-1 nfsd was able =
>> to listen on the IPV6 domain also.
>> Since 2.6.24 Main changes have been done to replace the way to make =
>> a socket for nfsd and lockd by replacing
>> svc_makesock routine by the *svc_create_xprt* service.
>>
>> Does anybody know if there is already a patch on this new code to =
>> support IPV6 for nfsd and lockd ?
>
>
> See:
>
> http://git.linux-nfs.org/?p=3Dcel/cel-2.6.git;a=3Dsummary
>
> There are patches that adjust svc_create_xprt() appropriately to take =
> an address family argument.
OK . I try them.
Thanks
>
> -- =
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
> -- =
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
-- =
-----------------------------------------------------------------
Company : Bull, Architect of an Open World TM (www.bull.com)
Name : Aime Le Rouzic =
Mail : Bull - BP 208 - 38432 Echirolles Cedex - France
E-Mail : aime.le-rouzic@bull.net
Phone : 33 (4) 76.29.75.51
Fax : 33 (4) 76.29.75.18
----------------------------------------------------------------- =
prev parent reply other threads:[~2008-05-28 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 9:47 svc_create_xprt for nfsd and lockd with ipv6 Le Rouzic
2008-05-27 14:27 ` Chuck Lever
2008-05-28 14:56 ` Le Rouzic [this message]
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=483D729C.307@bull.net \
--to=aime.le-rouzic@bull.net \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--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