From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: RDMAoE verbs questions Date: Tue, 1 Dec 2009 10:46:04 -0700 Message-ID: <20091201174604.GO1966@obsidianresearch.com> References: <2ED289D4E09FBD4D92D911E869B97FDD01CBE494@mtlexch01.mtl.com> <2ED289D4E09FBD4D92D911E869B97FDD01D0D6F9@mtlexch01.mtl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <2ED289D4E09FBD4D92D911E869B97FDD01D0D6F9-ia22CT07NJfiMCgWhms8HQC/G2K4zDHf@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Liran Liss Cc: Eli Cohen , Jeff Squyres , linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org On Tue, Dec 01, 2009 at 06:22:06PM +0200, Liran Liss wrote: > > Dealing with ABI compatability is a different issue, this new scheme > is API incompatible due to the change in semantics for existing values. > > For rdmacm applications, there are no semantic changes between IB and > RDMAoE. So? There are substantial semantic differences for *all* non-rdmacm applications. Even common ones like OpenMPI. You propose to ignore them? > > Please look at my message regarding using multiple devices, perhaps > you can improve on that general idea. > > RDMAoE *is* IB transport over Ethernet - we don't want different devices > with different node types exactly for this reason: applications > shouldn't care if they are running over IB or RDMAoE, and shouldn't add > another switch statement to support RDMAoE. Nonsense. RDMAoE is no such thing, it is utterly incompatible with the IB management model. It is some new protocol that is only about 90% compatible with IB. Apps using rdmacm shouldn't care one way or the other, apps that don't *need* a new transport type. 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