On Mon, Nov 30, 2009 at 09:03:47AM -0500, Jeff Squyres wrote: > Per my prior question: is it expected that IBoE will function > *exactly* the same as real IB? The addition of the port attribute > seems to imply not.
IBoE and IB should work exactly the same from the perspective of a user level application that makes use of rdmacm to create connections. Such apps can ignore the new attribute. And we believe this should cover the vast majority of apps. The new port attribute optionally allows the distinction for apps that need it (e.g. those that do not use the rdmacm, apps that have a reason to prefer one over the other when there is a choice, etc). > > Additionally, per Jason's question, why not simply expose this as an > additional device? E.g., can you APM across a real IB port and an > IBoE port on the same CX2? I'm guessing that they're *effectively* > different devices; it might make sense expose them as different > virtual device_t's. Just my $0.02. Yes. It should be possible to do APM across them. And with the ABI compatible link-protocol attribute we see no reason to force the isolation. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
