From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: Chuck Lever <chuck.lever@oracle.com>, Tom Tucker <tom@ogc.us>,
Steve Wise <swise@opengridcomputing.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH] svcrdma: RDMA support not yet compatible with RPC6
Date: Mon, 5 Apr 2010 12:16:18 -0400 [thread overview]
Message-ID: <20100405161618.GI16370@fieldses.org> (raw)
In-Reply-To: <4BBA06B8.3090201@opengridcomputing.com>
On Mon, Apr 05, 2010 at 10:50:16AM -0500, Tom Tucker wrote:
> J. Bruce Fields wrote:
>> On Mon, Apr 05, 2010 at 10:55:12AM -0400, Chuck Lever wrote:
>>
>>> On 04/03/2010 09:27 AM, Tom Tucker wrote:
>>>
>>>> RPC6 requires that it be possible to create endpoints that listen
>>>> exclusively for IPv4 or IPv6 connection requests. This is not currently
>>>> supported by the RDMA API.
>>>>
>>>> Signed-off-by: Tom Tucker<tom@opengridcomputing.com>
>>>> Tested-by: Steve Wise<swise@opengridcomputing.com>
>>>>
>>> Reviewed-by: Chuck Lever <chuck.lever@oracle.com>
>>>
>>
>> Thanks to all. I take it the problem began with 37498292a "NFSD: Create
>> PF_INET6 listener in write_ports"?
>>
>>
>
> Yes.
Thanks. I'll pass along
git://linux-nfs.org/~bfields/linux.git for-2.6.34
soon.
--b.
next prev parent reply other threads:[~2010-04-05 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 13:27 [PATCH] svcrdma: RDMA support not yet compatible with RPC6 Tom Tucker
2010-04-05 14:55 ` Chuck Lever
2010-04-05 15:48 ` J. Bruce Fields
2010-04-05 15:49 ` Chuck Lever
2010-04-05 15:50 ` Tom Tucker
2010-04-05 16:16 ` J. Bruce Fields [this message]
2010-04-05 16:20 ` J. Bruce Fields
2010-04-05 16:19 ` Tom Tucker
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=20100405161618.GI16370@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=swise@opengridcomputing.com \
--cc=tom@ogc.us \
--cc=tom@opengridcomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox