From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: nfsrdma broken on 2.6.34-rc1? Date: Mon, 29 Mar 2010 13:55:55 -0600 Message-ID: <20100329195555.GB28070@obsidianresearch.com> References: <4BB0E670.3010507@opengridcomputing.com> <20100329193715.GA28070@obsidianresearch.com> <4BB104D2.9080309@opengridcomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4BB104D2.9080309-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Steve Wise Cc: Roland Dreier , Sean Hefty , linux-rdma , Tom Tucker List-Id: linux-rdma@vger.kernel.org On Mon, Mar 29, 2010 at 02:51:46PM -0500, Steve Wise wrote: >> Yeah, exactly, it is very complex and there is a real need for >> things pretending to be IP to capture all this subtlety. The details >> can't just be skipped over, people will notice :( >> >> Though, I'm also not entirely certain that NFS-RDMA is right to bind >> to both AFs, generally speaking on Linux for a multi-protocol app you >> only want to bind to v6 addresses.. Or is it using IPV6_V6ONLY or alike? > This issue is really not in the NFS-RDMA code. the nfsd code is doing > the binding. See commit: > > 37498292aa97658a5d0a9bb84699ce8c1016bb74 > Author: Chuck Lever > Date: Tue Jan 26 14:04:22 2010 -0500 > > NFSD: Create PF_INET6 listener in write_ports Sure.. but it relies on the behavior of svcsock.c which does this: if (family == PF_INET6) kernel_setsockopt(sock, SOL_IPV6, IPV6_V6ONLY, (char *)&val, sizeof(val)); And the NFS-RDMA has no equivalent. Having the common code explicitly rely on IPV6_V6ONLY is quite troublesome when you can't implement it :) Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html