From: Weston Andros Adamson <dros@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: trond@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: NFS: pnfs ipv6 and multipath parsing
Date: Wed, 18 May 2011 16:19:38 -0400 [thread overview]
Message-ID: <74A7DF78-2AF3-43EA-978B-E53252045F04@netapp.com> (raw)
In-Reply-To: <AA6F9C64-8FDB-4B0A-B8CB-80AB4FA3D985@oracle.com>
Yeah, that should work too. Like other parts of fs/nfs/, I relied on rpc_pton() to allow or disallow parsing ipv6 addresses.
-dros
On May 18, 2011, at 4:11 PM, Chuck Lever wrote:
>
> On May 18, 2011, at 3:57 PM, Weston Andros Adamson wrote:
>
>> These two patches add support for IPv6 dataserver connectivity and
>> parsing all multipath addresses.
>>
>> IPv6: basically same patch as before:
>> - no longer calls kzalloc() while holding spinlock
>> - i verified that everything works as expected when CONFIG_IPV6 is not defined
>
> You'll also need to worry about when IPv6 is built in a kernel module, but ipv6.ko cannot be loaded.
>
> --
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
>
>
>
>
next prev parent reply other threads:[~2011-05-18 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 19:57 NFS: pnfs ipv6 and multipath parsing Weston Andros Adamson
2011-05-18 19:57 ` [PATCH 1/2] NFS: pnfs IPv6 support Weston Andros Adamson
2011-05-18 19:57 ` [PATCH 2/2] NFS: Parse and store all multipath DS addresses Weston Andros Adamson
2011-05-18 20:11 ` NFS: pnfs ipv6 and multipath parsing Chuck Lever
2011-05-18 20:19 ` Weston Andros Adamson [this message]
2011-05-18 20:29 ` Weston Andros Adamson
2011-05-18 20:41 ` Chuck Lever
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=74A7DF78-2AF3-43EA-978B-E53252045F04@netapp.com \
--to=dros@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond@netapp.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.